| 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: Fri, 12 Dec 2014 23:36:37 +0100 From: Paul Bolle <pebolle@...cali.nl> To: Andrew Morton <akpm@...ux-foundation.org> Cc: Stephen Rothwell <sfr@...b.auug.org.au>, Valentin Rothberg <valentinrothberg@...il.com>, linux-next@...r.kernel.org, linux-kernel@...r.kernel.org, Andy Lutomirski <luto@...capital.net>, Josh Triplett <josh@...htriplett.org> Subject: Re: linux-next: Tree for Dec 12 On Fri, 2014-12-12 at 13:57 -0800, Andrew Morton wrote: > On Fri, 12 Dec 2014 11:31:56 +0100 Paul Bolle <pebolle@...cali.nl> wrote: > > I won't be bothering (Andrew and) you again about this. Unless sorting > > this out takes rather long, that is. > > Is there some problem with the current mainline 3.19 code? The problem I noticed is with next-20141212. For some reason - Stephen appears to not know exactly why - it ended up with a Kconfig entry for INIT_FALLBACK without any actually users of that Kconfig symbol. My infamous 800 line perl monster - which I run on every linux-next release to check for exactly stuff like this - can't help but notice that. The idea being that my script notices these problems before they actually hit mainline. Note that the set of people actually worrying about this stuff contains me and, maybe, one or two other persons. Paul Bolle -- 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