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  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:	Thu, 6 Mar 2014 12:55:43 -0800 (PST)
From:	David Rientjes <>
To:	Tejun Heo <>
cc:	Andrew Morton <>,
	Johannes Weiner <>,
	Michal Hocko <>,
	KAMEZAWA Hiroyuki <>,
	Christoph Lameter <>,
	Pekka Enberg <>,
	Mel Gorman <>, Oleg Nesterov <>,
	Rik van Riel <>,
	Jianguo Wu <>,
	Tim Hockin <>,,,,
Subject: Re: [patch 00/11] userspace out of memory handling

On Thu, 6 Mar 2014, Tejun Heo wrote:

> On Tue, Mar 04, 2014 at 07:58:38PM -0800, David Rientjes wrote:
> > This patchset implements userspace out of memory handling.
> > 
> > It is based on v3.14-rc5.  Individual patches will apply cleanly or you
> > may pull the entire series from
> > 
> > 	git:// mm/oom
> > 
> > When the system or a memcg is oom, processes running on that system or
> > attached to that memcg cannot allocate memory.  It is impossible for a
> > process to reliably handle the oom condition from userspace.
> ISTR the conclusion last time was nack on the whole approach.  What
> changed between then and now?  I can't detect any fundamental changes
> from the description.

This includes system oom handling alongside memcg oom handling.  If you 
have specific objections, please let us know, thanks!
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists