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 16:12:46 -0500
From:	Tejun Heo <>
To:	David Rientjes <>
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 07/11] mm, memcg: allow processes handling oom
 notifications to access reserves

On Tue, Mar 04, 2014 at 07:59:29PM -0800, David Rientjes wrote:
> Now that a per-process flag is available, define it for processes that
> handle userspace oom notifications.  This is an optimization to avoid
> mantaining a list of such processes attached to a memcg at any given time
> and iterating it at charge time.
> This flag gets set whenever a process has registered for an oom
> notification and is cleared whenever it unregisters.
> When memcg reclaim has failed to free any memory, it is necessary for
> userspace oom handlers to be able to dip into reserves to pagefault text,
> allocate kernel memory to read the "tasks" file, allocate heap, etc.
> System oom conditions are not addressed at this time, but the same per-
> process flag can be used in the page allocator to determine if access
> should be given to userspace oom handlers to per-zone memory reserves at
> a later time once there is consensus.
> Signed-off-by: David Rientjes <>

ntil consensus on the whole approach can be reached,

 Nacked-by: Tejun Heo <>


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