lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 10 Mar 2011 20:00:54 -0500 From: Mike Frysinger <vapier.adi@...il.com> To: Andrew Morton <akpm@...ux-foundation.org> Cc: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>, Michal Marek <mmarek@...e.cz>, Sam Ravnborg <sam@...nborg.org>, linux-kernel@...r.kernel.org, kernel@...gutronix.de, linux-arm-kernel@...ts.infradead.org Subject: Re: [PATCH] kbuild: reenable section mismatch analysis 2011/3/10 Andrew Morton : > On Fri, 18 Feb 2011 21:47:20 +0100 Uwe Kleine-K__nig wrote: >> This was disabled in commit >> >> e5f95c8 (kbuild: print only total number of section mismatces found) >> >> because there were too many warnings. Now we're down to a reasonable >> number again, so we start scaring people with the details. >> >> --- a/lib/Kconfig.debug >> +++ b/lib/Kconfig.debug >> @@ -102,11 +102,7 @@ config HEADERS_CHECK >> >> config DEBUG_SECTION_MISMATCH >> bool "Enable full Section mismatch analysis" >> - depends on UNDEFINED || (BLACKFIN) >> default y >> - # This option is on purpose disabled for now. >> - # It will be enabled when we are down to a reasonable number >> - # of section mismatch warnings (< 10 for an allyesconfig build) >> help >> The section mismatch analysis checks if there are illegal >> references from one section to another section. > > eaaaargh! 650 lines of crap added to my i386 allmodconfig build output. and it's going to keep staying all f-ed up until people start seeing this stuff themselves when they write the bad code -mike -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists