Buildresult: linus/i386-allnoconfig/i386-gcc4.6 built on Jun 14 2018, 18:01

kisskb

Revisions | Branches | Compilers | Configs | Build Results | Build Failures |

Status:	OK
Date/Time:	Jun 14 2018, 18:01
Duration:	0:00:17.381013
Builder:	ka4
Revision:	Kbuild: rename CC_STACKPROTECTOR[_STRONG] config variables (`050e9baa9dc9fbd9ce2b27f0056990fc9e0a08a0)`
Target:	linus/i386-allnoconfig/i386-gcc4.6
Branch:	linus
Compiler:	i386-gcc4.6 (i386-linux-gcc (GCC) 4.6.3)
Config:	allnoconfig (download)
Log:	Download original Possible warnings (2) kernel/printk/printk.c:183:16: warning: 'old' may be used uninitialized in this function [-Wuninitialized] arch/x86/kernel/e820.c:651:16: warning: 'gapstart' may be used uninitialized in this function [-Wuninitialized] Full Log # git rev-parse -q --verify 050e9baa9dc9fbd9ce2b27f0056990fc9e0a08a0^{commit} 050e9baa9dc9fbd9ce2b27f0056990fc9e0a08a0 already have revision, skipping fetch # git checkout -q -f -B kisskb 050e9baa9dc9fbd9ce2b27f0056990fc9e0a08a0 # git clean -qxdf # < git log -1 # commit 050e9baa9dc9fbd9ce2b27f0056990fc9e0a08a0 # Author: Linus Torvalds <torvalds@linux-foundation.org> # Date: Thu Jun 14 12:21:18 2018 +0900 # # Kbuild: rename CC_STACKPROTECTOR[_STRONG] config variables # # The changes to automatically test for working stack protector compiler # support in the Kconfig files removed the special STACKPROTECTOR_AUTO # option that picked the strongest stack protector that the compiler # supported. # # That was all a nice cleanup - it makes no sense to have the AUTO case # now that the Kconfig phase can just determine the compiler support # directly. # # HOWEVER. # # It also meant that doing "make oldconfig" would now _disable_ the strong # stackprotector if you had AUTO enabled, because in a legacy config file, # the sane stack protector configuration would look like # # CONFIG_HAVE_CC_STACKPROTECTOR=y # # CONFIG_CC_STACKPROTECTOR_NONE is not set # # CONFIG_CC_STACKPROTECTOR_REGULAR is not set # # CONFIG_CC_STACKPROTECTOR_STRONG is not set # CONFIG_CC_STACKPROTECTOR_AUTO=y # # and when you ran this through "make oldconfig" with the Kbuild changes, # it would ask you about the regular CONFIG_CC_STACKPROTECTOR (that had # been renamed from CONFIG_CC_STACKPROTECTOR_REGULAR to just # CONFIG_CC_STACKPROTECTOR), but it would think that the STRONG version # used to be disabled (because it was really enabled by AUTO), and would # disable it in the new config, resulting in: # # CONFIG_HAVE_CC_STACKPROTECTOR=y # CONFIG_CC_HAS_STACKPROTECTOR_NONE=y # CONFIG_CC_STACKPROTECTOR=y # # CONFIG_CC_STACKPROTECTOR_STRONG is not set # CONFIG_CC_HAS_SANE_STACKPROTECTOR=y # # That's dangerously subtle - people could suddenly find themselves with # the weaker stack protector setup without even realizing. # # The solution here is to just rename not just the old RECULAR stack # protector option, but also the strong one. This does that by just # removing the CC_ prefix entirely for the user choices, because it really # is not about the compiler support (the compiler support now instead # automatially impacts _visibility_ of the options to users). # # This results in "make oldconfig" actually asking the user for their # choice, so that we don't have any silent subtle security model changes. # The end result would generally look like this: # # CONFIG_HAVE_CC_STACKPROTECTOR=y # CONFIG_CC_HAS_STACKPROTECTOR_NONE=y # CONFIG_STACKPROTECTOR=y # CONFIG_STACKPROTECTOR_STRONG=y # CONFIG_CC_HAS_SANE_STACKPROTECTOR=y # # where the "CC_" versions really are about internal compiler # infrastructure, not the user selections. # # Acked-by: Masahiro Yamada <yamada.masahiro@socionext.com> # Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> # < /opt/cross/kisskb/gcc-4.6.3-nolibc/i386-linux/bin/i386-linux-gcc --version # < git log --format=%s --max-count=1 050e9baa9dc9fbd9ce2b27f0056990fc9e0a08a0 # < make -s -j 10 ARCH=i386 O=/kisskb/build/linus_i386-allnoconfig_i386 CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/i386-linux/bin/i386-linux- allnoconfig # make -s -j 10 ARCH=i386 O=/kisskb/build/linus_i386-allnoconfig_i386 CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/i386-linux/bin/i386-linux- /kisskb/src/net/Makefile:24: CC cannot link executables. Skipping bpfilter. /kisskb/src/kernel/printk/printk.c: In function 'devkmsg_sysctl_set_loglvl': /kisskb/src/kernel/printk/printk.c:183:16: warning: 'old' may be used uninitialized in this function [-Wuninitialized] /kisskb/src/arch/x86/kernel/e820.c: In function 'e820__setup_pci_gap': /kisskb/src/arch/x86/kernel/e820.c:651:16: warning: 'gapstart' may be used uninitialized in this function [-Wuninitialized] Completed OK # rm -rf /kisskb/build/linus_i386-allnoconfig_i386 # Build took: 0:00:17.381013

© Michael Ellerman 2006-2018.