linux-kernel - Re: [Ksummit-2013-discuss] [ATTEND] How to act on LKML

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 17 Jul 2013 18:57:21 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Stefano Stabellini <stefano.stabellini@...citrix.com>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	Sarah Sharp <sarah.a.sharp@...ux.intel.com>,
	CAI Qian <caiqian@...hat.com>, David Lang <david@...g.hm>,
	ksummit-2013-discuss@...ts.linuxfoundation.org,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Darren Hart <dvhart@...ux.intel.com>,
	Olivier Galibert <galibert@...ox.com>,
	stable <stable@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Willy Tarreau <w@....eu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...nel.org>
Subject: Re: [Ksummit-2013-discuss] [ATTEND] How to act on LKML

On Wed, Jul 17, 2013 at 06:00:46PM +0100, Stefano Stabellini wrote:
> On Wed, 17 Jul 2013, Steven Rostedt wrote:
> > The last thing I want to do is to lower the quality of the kernel just
> > to get a wider range of developers.
> 
> Can we stop bringing the quality of the code into the discussion?

No.

> I think it's pretty clear that one doesn't need to be verbally abusive
> in order to stop bad code from getting into the kernel.

At the risk of sounding pedantic...  The above is true *and* irrelevant
as stated, and any attempts to read it in less irrelevant way result
in statements that are absolutely non-obvious and very likely false.
	* some amount of bad code will be getting into the kernel, in
any scenario short of complete cessation of development
	* there certainly are ways to prevent any given bad code from
getting into the kernel, once you have identified it.  Even leaving
aside completely ridiculous ones ("after WW3 nobody will push that into
the tree", etc.), one can always watch all trees for specific code and
refuse to pull if it has slipped in.
	* "once you have identified it" part of the above is essential
and does not scale.
In other words, it's not "can we stop it from happening", it's "how
much will be slippling in with given setup".  And _this_ is where your
position becomes completely unfounded.  It's not at all clear that
vague alternatives being proposed will *not* result in more crap getting
in.
--
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/