linux-kernel - Re: [PATCH 0/4] make vfork() killable

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: <20120216162602.386cadf9.akpm@linux-foundation.org>
Date:	Thu, 16 Feb 2012 16:26:02 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	apw@...onical.com, arjan@...ux.intel.com, fhrbata@...hat.com,
	john.johansen@...onical.com, penguin-kernel@...ove.SAKURA.ne.jp,
	rientjes@...gle.com, rusty@...tcorp.com.au, tj@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] make vfork() killable

On Thu, 16 Feb 2012 18:26:26 +0100
Oleg Nesterov <oleg@...hat.com> wrote:

> On 02/16, Oleg Nesterov wrote:
> >
> > Btw, there is another example of "unbounded" sleep in UNINTERRUPTIBLE,
> > vfork. I already have the patches, will send today.
> 
> Make vfork() killable, please apply.
> 
> These patches are old (Aug 2011), they spent a lot of time in linux-next
> without any problem. Linus participated in the discussion, iiuc he has
> no objections.

hum.  Via which tree did they get into linux-next and why did they not
get any further?

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