linux-kernel - Re: [PATCH 0/5] do_wait cleanupe (more to come)

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] [day] [month] [year] [list]

Message-Id: <20090511113505.ca9384af.akpm@linux-foundation.org>
Date:	Mon, 11 May 2009 11:35:05 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	oleg@...hat.com, roland@...hat.com, vmayatsk@...hat.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] do_wait cleanupe (more to come)

On Mon, 11 May 2009 14:22:33 +0200
Ingo Molnar <mingo@...e.hu> wrote:

> 
> * Andrew Morton <akpm@...ux-foundation.org> wrote:
> 
> > On Thu, 7 May 2009 08:46:30 +0200
> > Oleg Nesterov <oleg@...hat.com> wrote:
> > 
> > > Slightly tested. Definitely this needs more testing, but since a) the
> > > second patch was reviewed by Ingo and b) Andrew likes the buggy patches
> > > very much, I am sending this series. At least I believe this all is
> > > right "in general".
> > 
> > Worried.  This hits on ptrace and there's a lot of ptrace work 
> > pending, including large changes which are threatening to come in 
> > via a different tree (security).
> > 
> > If we end up with marginal/flakey patches in the middle of all of 
> > this, a big mess ensues.
> 
> This problems would be solved if all these bits were in -mm.
> 

I merged them, but that didn't solve the problem.  If more ptrace work
happens and then these patches turn out to be bad, we have a mess on
our hands.

IOW, merging "Slightly tested.  Definitely this needs more testing"
patches into an area on ongoing development is a bit risky.
--
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/