Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
接近 2 年 前同步成功

通知 170
Star 36
Fork 7
cloud-kernel
cloud-kernel
切换分支/标签
  1. 19 2月, 2016 1 次提交
  3. 18 2月, 2016 1 次提交
  5. 21 1月, 2016 5 次提交
  7. 16 1月, 2016 1 次提交
  9. 15 1月, 2016 2 次提交
  11. 13 1月, 2016 5 次提交
  13. 12 1月, 2016 1 次提交
    • L
      kbuild: Demote 'sign-compare' warning to W=2 · 7599ea8b
      由 Lee Jones 提交于 
      Ideally, a kernel compile with W=1 enabled should complete cleanly;
however, when we run one currently we are presented with ~25k warnings.
'sign-compare' accounts for ~22k of those ~25k.

In this patch we're demoting 'sign-compare' warnings to W=2, with a view
to fixing the remaining 3k W=1 warnings required for a clean build.

Arnd adds:
  "As per our discussion, I'd add that this was inadvertedly introduced
   by Behan when he moved the clang specific warnings into an ifdef block
   and did not notice that -Wsign-compare was interpreted by both gcc
   and clang.

   Earlier, it was introduced in just the same way by Jan-Simon as part
   of 3d3d6b84 ("kbuild: LLVMLinux: Adapt warnings for compilation
   with clang")."
Acked-by: NArnd Bergmann <arnd@arndb.de>
Fixes: 26ea6bb1 ("kbuild, LLVMLinux: Supress warnings unless W=1-3")
Signed-off-by: NLee Jones <lee.jones@linaro.org>
Signed-off-by: NMichal Marek <mmarek@suse.com>
      7599ea8b
  15. 11 1月, 2016 2 次提交
    • C
      kconfig: fix qconf segfault by deleting heap objects · 5b61c7bd
      由 Chris Bainbridge 提交于 
      On Debian stable (qt-4.8.6) 'make xconfig' intermittently fails due to
qconf segfaulting at exit time in QXcbEventReader. The cause of this is
destructors on the heap objects never being called, so fix this by
properly deleting the heap objects before exit.
Signed-off-by: NChris Bainbridge <chris.bainbridge@gmail.com>
Signed-off-by: NMichal Marek <mmarek@suse.com>
      5b61c7bd
    • V
      um: link with -lpthread · a7df4716
      由 Vegard Nossum 提交于 
      Similarly to commit fb1770aa, with gcc 5
on Ubuntu and CONFIG_STATIC_LINK=y I was seeing these linker errors:

/usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/librt.a(timer_create.o): In function `__timer_create_new':
(.text+0xcd): undefined reference to `pthread_once'
/usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/librt.a(timer_create.o): In function `__timer_create_new':
(.text+0x126): undefined reference to `pthread_attr_init'
/usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/librt.a(timer_create.o): In function `__timer_create_new':
(.text+0x168): undefined reference to `pthread_attr_setdetachstate'
[...]

Obviously we also need -lpthread for librt.a.

Cc: stable@vger.kernel.org # 4.4
Signed-off-by: NVegard Nossum <vegard.nossum@oracle.com>
Signed-off-by: NRichard Weinberger <richard@nod.at>
      a7df4716
  17. 08 1月, 2016 1 次提交
  19. 06 1月, 2016 6 次提交
    • M
      tags: Unify emacs and exuberant rules · 93209d65
      由 Michal Marek 提交于 
      The emacs rules were constantly lagging behind the exuberant ones. Use a
single set of rules for both, to make the script easier to maintain.
The language understood by both tools is basic regular expression with
some limitations, which are documented in a comment. To be able to store
the rules in an array and easily iterate over it, the script requires
bash now. In the exuberant case, the change fixes some false matches in
<linux/page-flags.h> and also some too greedy matches in the arguments
of the DECLARE_*/DEFINE_* macros. In the emacs case, several previously
not working rules are matching now. Tested with these versions of the
tools:

  Exuberant Ctags 5.8, Copyright (C) 1996-2009 Darren Hiebert
  etags (GNU Emacs 24.5)
Signed-off-by: NMichal Marek <mmarek@suse.com>
      93209d65
    • M
      tags: Drop the _PE rule · a1ccdb63
      由 Michal Marek 提交于 
      We are not indexing the userspace tools, so the rules only match some
false positives in the kernel code.
Signed-off-by: NMichal Marek <mmarek@suse.com>
      a1ccdb63
    • M
      tags: Do not try to index defconfigs · ab9ca615
      由 Michal Marek 提交于 
      The defconfig files are in predictable locations, so there is no need to
index them. Plus, the script was only looking for files named
'defconfig', which only works on a few architectures nowadays.
Signed-off-by: NMichal Marek <mmarek@suse.com>
      ab9ca615
    • M
      tags: Process Kconfig files in a single pass · a281b856
      由 Michal Marek 提交于 
      Signed-off-by: NMichal Marek <mmarek@suse.com>
      a281b856
    • M
      tags: Fix erroneous pattern match in a comment · c26206f2
      由 Michal Marek 提交于 
      Apparently, ctags applies the rules before deleting comments:

ctags: Warning: include/linux/completion.h:22: null expansion of name pattern "\2"

Work around this particular case by requiring the group to contain at
least one character. Leave the other patters as they are, until a better
solution is found.
Signed-off-by: NMichal Marek <mmarek@suse.com>
      c26206f2
    • M
      tags: Treat header files as C code · d2fb5aed
      由 Michal Marek 提交于 
      This allows to apply the same patters to both source and header files.
The effect is mostly visible in the case of DECLARE_BITMAP, but there
are small gains all over the place. There is also lots of random changes
in the diff, I believe this is simply because there are still lots of
unexpanded macros in the code and the C and C++ parsers fail and recover
at different points. Also, qconf.h is parsed as C, but that's a
negligible regression.
Signed-off-by: NMichal Marek <mmarek@suse.com>
      d2fb5aed
  21. 05 1月, 2016 2 次提交
  23. 04 1月, 2016 1 次提交
  25. 18 12月, 2015 1 次提交
  27. 17 12月, 2015 1 次提交
    • S
      ftrace/scripts: Have recordmcount copy the object file · a50bd439
      由 Steven Rostedt (Red Hat) 提交于 
      Russell King found that he had weird side effects when compiling the kernel
with hard linked ccache. The reason was that recordmcount modified the
kernel in place via mmap, and when a file gets modified twice by
recordmcount, it will complain about it. To fix this issue, Russell wrote a
patch that checked if the file was hard linked more than once and would
unlink it if it was.

Linus Torvalds was not happy with the fact that recordmcount does this in
place modification. Instead of doing the unlink only if the file has two or
more hard links, it does the unlink all the time. In otherwords, it always
does a copy if it changed something. That is, it does the write out if a
change was made.

Cc: stable@vger.kernel.org # 2.6.37+
Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      a50bd439
  29. 16 12月, 2015 1 次提交
  31. 15 12月, 2015 3 次提交
  33. 10 12月, 2015 1 次提交
  35. 09 12月, 2015 2 次提交
    • M
      genksyms: Handle string literals with spaces in reference files · a78f70e8
      由 Michal Marek 提交于 
      The reference files use spaces to separate tokens, however, we must
preserve spaces inside string literals. Currently the only case in the
tree is struct edac_raw_error_desc in <linux/edac.h>:

$ KBUILD_SYMTYPES=1 make -s drivers/edac/amd64_edac.symtypes
$ mv drivers/edac/amd64_edac.{symtypes,symref}
$ KBUILD_SYMTYPES=1 make -s drivers/edac/amd64_edac.symtypes
drivers/edac/amd64_edac.c:527: warning: amd64_get_dram_hole_info: modversion changed because of changes in struct edac_raw_error_desc
Signed-off-by: NMichal Marek <mmarek@suse.com>
      a78f70e8
    • L
      arch: um: fix error when linking vmlinux. · fb1770aa
      由 Lorenzo Colitti 提交于 
      On gcc Ubuntu 4.8.4-2ubuntu1~14.04, linking vmlinux fails with:

arch/um/os-Linux/built-in.o: In function `os_timer_create':
/android/kernel/android/arch/um/os-Linux/time.c:51: undefined reference to `timer_create'
arch/um/os-Linux/built-in.o: In function `os_timer_set_interval':
/android/kernel/android/arch/um/os-Linux/time.c:84: undefined reference to `timer_settime'
arch/um/os-Linux/built-in.o: In function `os_timer_remain':
/android/kernel/android/arch/um/os-Linux/time.c:109: undefined reference to `timer_gettime'
arch/um/os-Linux/built-in.o: In function `os_timer_one_shot':
/android/kernel/android/arch/um/os-Linux/time.c:132: undefined reference to `timer_settime'
arch/um/os-Linux/built-in.o: In function `os_timer_disable':
/android/kernel/android/arch/um/os-Linux/time.c:145: undefined reference to `timer_settime'

This is because -lrt appears in the generated link commandline
after arch/um/os-Linux/built-in.o. Fix this by removing -lrt from
arch/um/Makefile and adding it to the UM-specific section of
scripts/link-vmlinux.sh.
Signed-off-by: NLorenzo Colitti <lorenzo@google.com>
Signed-off-by: NRichard Weinberger <richard@nod.at>
      fb1770aa
  37. 07 12月, 2015 1 次提交
  39. 25 11月, 2015 2 次提交
    • M
      kbuild: Allow to specify composite modules with modname-m · cf4f2193
      由 Michal Marek 提交于 
      This allows to write

  drm-$(CONFIG_AGP) += drm_agpsupport.o

without having to handle CONFIG_AGP=y vs. CONFIG_AGP=m. Only support
this syntax for modules, since built-in code depending on something
modular cannot work and init/Makefile actually relies on the current
semantics. There are a few drivers which adapted to the current
semantics out of necessity; these are fixed to also work when the
respective subsystem is modular.

Acked-by: Peter Chen <peter.chen@freescale.com> [chipidea]
Signed-off-by: NMichal Marek <mmarek@suse.com>
      cf4f2193
    • R
      package Makefile: fix perf-tar targets when outdir is set · 4b63f603
      由 Riku Voipio 提交于 
      building with $srctree != $objtree, perf-tar-* targets fail
to read the MANIFEST file and add the PERF-VERSION-FILE needed
by out-of-tree builds. The build errors and an incorrect tar is created:

$ make O=build-x86 perf-targz-src-pkg
  TAR
cat: ../tools/perf/MANIFEST: No such file or directory
tar: perf-4.1.0-rc8/PERF-VERSION-FILE: Cannot stat: No such file or
dir..
tar: Exiting with failure status due to previous errors

Kbuild sets objtree to "." and srctree to ".." The command to output
MANIFEST becomes:

   $(cd ..; echo $(cat ../tools/perf/MANIFEST))

Without MANIFEST, the entire kernel source tree is added to the perf
source tarball. The *correct* fix is to keep the cd and remove srctree
from cat command line since MANIFEST has wildcards that fail to expand
working directory isn't srctree.

Second, PERF-VERSION-FILE gets not added, because in-tree build path is
hardcoded to Makefile:

   util/PERF-VERSION-GEN ../../$(perf-tar)/ 2>/dev/null)

The PERF-VERSION-GEN needs to be run from tools/perf directory,
and the output directory needs to be changed from relative to
to absolute. This can be achieved using the $(CURDIR) variable.

Also remove the error redirect to /dev/null which hid the error.
Signed-off-by: NRiku Voipio <riku.voipio@linaro.org>
Signed-off-by: NMichal Marek <mmarek@suse.com>
      4b63f603