Re: [patch 1/2] mm, memcg: avoid oom notification when current needs access to memory reserves

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: David Rientjes <rientjes@xxxxxxxxxx>
Subject: Re: [patch 1/2] mm, memcg: avoid oom notification when current needs access to memory reserves
From: Greg Kroah-Hartmann <gregkh@xxxxxxxxxxxxxxxxxxx>
Date: Mon, 20 Jan 2014 22:04:28 -0800
Authentication-results: mx.google.com; spf=pass (google.com: domain of gregkh@xxxxxxxxxxxxxxxxxxx designates 140.211.169.12 as permitted sender) smtp.mail=gregkh@xxxxxxxxxxxxxxxxxxx
Cc: Michal Hocko <mhocko@xxxxxxx>, Johannes Weiner <hannes@xxxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, cgroups@xxxxxxxxxxxxxxx, "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
Delivered-to: linux-mm-outgoing@xxxxxxxxx
In-reply-to: <alpine.DEB.2.02.1401202155410.21729@chino.kir.corp.google.com>
User-agent: Mutt/1.5.22 (2013-10-16)

On Mon, Jan 20, 2014 at 09:58:28PM -0800, David Rientjes wrote:
> The patches getting proposed through -mm for stable boggles my mind
> sometimes.

Do you have any objections to patches that I have taken for -stable?  If
so, please let me know.

thanks,

greg k-h

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>

Follow-Ups:
- Re: [patch 1/2] mm, memcg: avoid oom notification when current needs access to memory reserves
  - From: David Rientjes

References:
- Re: [patch 1/2] mm, memcg: avoid oom notification when current needs access to memory reserves
  - From: Andrew Morton
- Re: [patch 1/2] mm, memcg: avoid oom notification when current needs access to memory reserves
  - From: David Rientjes
- Re: [patch 1/2] mm, memcg: avoid oom notification when current needs access to memory reserves
  - From: Andrew Morton
- Re: [patch 1/2] mm, memcg: avoid oom notification when current needs access to memory reserves
  - From: David Rientjes
- Re: [patch 1/2] mm, memcg: avoid oom notification when current needs access to memory reserves
  - From: Johannes Weiner
- Re: [patch 1/2] mm, memcg: avoid oom notification when current needs access to memory reserves
  - From: David Rientjes
- Re: [patch 1/2] mm, memcg: avoid oom notification when current needs access to memory reserves
  - From: Michal Hocko
- Re: [patch 1/2] mm, memcg: avoid oom notification when current needs access to memory reserves
  - From: David Rientjes
- Re: [patch 1/2] mm, memcg: avoid oom notification when current needs access to memory reserves
  - From: Michal Hocko
- Re: [patch 1/2] mm, memcg: avoid oom notification when current needs access to memory reserves
  - From: David Rientjes

Prev by Date: Re: [patch 1/2] mm, memcg: avoid oom notification when current needs access to memory reserves
Next by Date: Re: [patch 1/2] mm, memcg: avoid oom notification when current needs access to memory reserves
Previous by thread: Re: [patch 1/2] mm, memcg: avoid oom notification when current needs access to memory reserves
Next by thread: Re: [patch 1/2] mm, memcg: avoid oom notification when current needs access to memory reserves
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux] [Linux OMAP] [Linux MIPS] [ECOS] [Asterisk Internet PBX] [Linux API]