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]
Message-ID: <m1ab0tcwep.fsf@fess.ebiederm.org>
Date:	Thu, 17 Sep 2009 10:29:18 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Greg KH <greg@...ah.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Kay Sievers <kay.sievers@...y.org>
Subject: Re: [PATCH] Remove broken by design and by implementation devtmpfs maintenance disaster

Greg KH <greg@...ah.com> writes:

> On Thu, Sep 17, 2009 at 01:23:39AM -0700, Eric W. Biederman wrote:
>> 
>> devtmpfs has numerous problems.  The once I see from a quick review.
>
> <snip>
>
> I'm confused, why did you not at least cc: Kay and I on this message, if
> I was a paranoid person, I would think that you were somehow trying to
> skirt around us for some unknown reason :(

You just aren't relevant to this discussion except where you
repeatedly demonstrate you aren't willing to listen to anyone who
hasn't drunk the devtmpfs coolaid.

If you were interested in honest review and feedback you would have
copied me from the second review onward.  You didn't do that.  Why
should I extend you the courtesy.  This isn't your decision to make.

> I think Kay has raised the proper points already.

Kay blithely replied to my points but he wasn't paying attention, and
certainly did not look at how what I have said applies to the code. 

Greg this code does not live up to the standards you have repeatedly
asserted are required for accepting core kernel code.  Neither you
nor Kay show any interest in fixing even the most trivial of bugs.
Must less discuss alternate solutions to the problem.

My recommendation stands as you are unwilling to fix bugs and listen
to other peoples opinion merging the code at this time is a bad idea.

Eric
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ