From: Greg KH <greg@kroah.com>
To: nishimura@mxp.nes.nec.co.jp
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
stable <stable@kernel.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: Re: [stable] [BUGFIX][PATCH v3] memcg: avoid oom-killing innocent task in case of use_hierarchy
Date: Tue, 5 Jan 2010 11:26:17 -0800 [thread overview]
Message-ID: <20100105192617.GA9681@kroah.com> (raw)
In-Reply-To: <20100105122633.28738255.d-nishimura@mtf.biglobe.ne.jp>
On Tue, Jan 05, 2010 at 12:26:33PM +0900, Daisuke Nishimura wrote:
> On Mon, 4 Jan 2010 14:28:19 -0800
> Greg KH <greg@kroah.com> wrote:
>
> > On Thu, Dec 17, 2009 at 09:47:24AM +0900, Daisuke Nishimura wrote:
> > > Stable team.
> > >
> > > Cay you pick this up for 2.6.32.y(and 2.6.31.y if it will be released) ?
> > >
> > > This is a for-stable version of a bugfix patch that corresponds to the
> > > upstream commmit d31f56dbf8bafaacb0c617f9a6f137498d5c7aed.
> >
> > I've applied it to the .32-stable tree, but it does not apply to .31.
> > Care to provide a version of the patch for that kernel if you want it
> > applied there?
> >
> hmm, strange. I can apply it onto 2.6.31.9. It might conflict with other patches
> in 2.6.31.y queue ?
> Anyway, I've attached the patch that is rebased on 2.6.31.9. Please tell me if you
> have any problem with it.
>
> v3: rebased on 2.6.31.9
This version worked, thanks for regenerating it.
greg k-h
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-01-05 19:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 5:57 [BUGFIX][PATCH -mmotm] memcg: avoid oom-killing innocent task in case of use_hierarchy Daisuke Nishimura
2009-11-24 7:28 ` [BUGFIX][PATCH -stable] " Daisuke Nishimura
2009-11-25 0:00 ` KAMEZAWA Hiroyuki
2009-11-25 5:32 ` [BUGFIX][PATCH v2 " Daisuke Nishimura
2009-11-25 5:50 ` KAMEZAWA Hiroyuki
2009-11-25 20:45 ` Andrew Morton
2009-11-26 0:11 ` [BUGFIX][PATCH v2 -mmotm] " Daisuke Nishimura
2009-12-17 0:47 ` [BUGFIX][PATCH v2 -stable] " Daisuke Nishimura
2010-01-04 22:28 ` [stable] " Greg KH
2010-01-05 3:26 ` [stable][BUGFIX][PATCH v3] " Daisuke Nishimura
2010-01-05 19:26 ` Greg KH [this message]
2010-01-05 19:33 ` patch memcg-avoid-oom-killing-innocent-task-in-case-of-use_hierarchy.patch added to 2.6.31-stable tree gregkh
2009-11-25 4:08 ` [BUGFIX][PATCH -stable] memcg: avoid oom-killing innocent task in case of use_hierarchy Balbir Singh
2009-11-24 13:31 ` [BUGFIX][PATCH -mmotm] " Balbir Singh
2009-11-24 14:00 ` Daisuke Nishimura
2009-11-24 17:04 ` Balbir Singh
2009-11-24 23:49 ` Daisuke Nishimura
2009-11-25 3:29 ` Balbir Singh
2009-11-25 0:07 ` KAMEZAWA Hiroyuki
2009-11-25 4:09 ` Balbir Singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100105192617.GA9681@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=rientjes@google.com \
--cc=stable@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).