linux-kernel - Re: [patch 00/13] devtmpfs patches

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:	Mon, 11 May 2009 11:55:04 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Kay Sievers <kay.sievers@...y.org>
Cc:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Arjan van de Ven <arjan@...radead.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Greg KH <gregkh@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Fabio Comolli <fabio.comolli@...il.com>,
	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org
Subject: Re: [patch 00/13] devtmpfs patches

> I would be very careful with such statement if you want us to accept
> your namespace hacks in the future. I guess if we ask with your next
> round "do we want to to have to maintain this for forever" you get a
> very different answer than today.

Take your unpleasant threatening attitude somewhere else. There are a lot
of people very interested in namespaces.

> > I'm sorry you decided to ship the code before getting a review.  I
> > guess that is the definition of an experimental feature.  One not in
> > the upstream kernel.
> 
> No, I did decide to ship it in the distro which is how things work
> since forever. And it's not in the upstream kernel now, while this
> discussion happens.

And since forever the upstream approach has been "we don't care if you
shipped it first, that's *your* problem"

You've yet to demonstrate
- That your patches are a real speed up
- That dumping more crap in kernel without policy and management is a
  good idea
- That the other proposals are worse than yours.

Arjan produced detailed boot graphs and boots a box very fast indeed. I
see no boot graphs, no detailed analysis here. 

Instead we have obnoxious threats to Eric Biederman and an "I am going to
ram this into the kernel whatever" approach.

Neither are constructive or useful and this isn't the way the Linux
kernel project works. Yes maybe you can stuff things into Greg's tree
easily because you both work for SuSE but that isn't the right way to do
stuff for upstream.

Alan
--
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/