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-next>] [day] [month] [year] [list]
Date:	Wed, 20 Nov 2013 00:05:18 -0800 (PST)
From:	David Rientjes <rientjes@...gle.com>
To:	linux-kernel@...r.kernel.org
cc:	mm-commits@...r.kernel.org, mhocko@...e.cz,
	kamezawa.hiroyu@...fujitsu.com, hannes@...xchg.org
Subject: Re: [to-be-updated] mm-memcg-add-memoryoom_control-notification-for-system-oom.patch
 removed from -mm tree

On Tue, 19 Nov 2013, akpm@...ux-foundation.org wrote:

> Subject: [to-be-updated] mm-memcg-add-memoryoom_control-notification-for-system-oom.patch removed from -mm tree
> To: rientjes@...gle.com,hannes@...xchg.org,kamezawa.hiroyu@...fujitsu.com,mhocko@...e.cz,mm-commits@...r.kernel.org
> From: akpm@...ux-foundation.org
> Date: Tue, 19 Nov 2013 13:38:14 -0800
> 
> 
> The patch titled
>      Subject: mm, memcg: add memory.oom_control notification for system oom
> has been removed from the -mm tree.  Its filename was
>      mm-memcg-add-memoryoom_control-notification-for-system-oom.patch
> 
> This patch was dropped because an updated version will be merged

Why is this removed?

I've laid out my perspective for doing userspace oom handling and this is 
a vital part for system oom handling.  I know that we are currently 
discussing alternative proposals but my proposal is by far the most 
complete and allows the most powerful policies to be implemented in 
userspace.  I'd prefer if we would keep the patch unless an actual 
alternative is proposed and agreed upon, we can still discuss alternatives 
while this in -mm and this patch in no way precludes other mechanisms from 
being implemented.

So why remove this?
--
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