All of lore.kernel.org
 help / color / mirror / Atom feed
From: <gregkh@suse.de>
To: d-nishimura@mtf.biglobe.ne.jp, akpm@linux-foundation.org,
	balbir@linux.vnet.ibm.com, gregkh@suse.de, greg@kroah.com,
	kamezawa.hiroyu@jp.fujitsu.com, kosaki.motohiro@jp.fujitsu.com,
	linux-mm@kvack.org, nishimura@mxp.nes.nec.co.jp,
	rientjes@google.com, stable@kernel.org
Cc: stable-commits@vger.kernel.org
Subject: patch memcg-avoid-oom-killing-innocent-task-in-case-of-use_hierarchy.patch added to 2.6.31-stable tree
Date: Tue, 05 Jan 2010 11:33:04 -0800	[thread overview]
Message-ID: <12627199842369@kroah.org> (raw)
In-Reply-To: <20100105122633.28738255.d-nishimura@mtf.biglobe.ne.jp>


This is a note to let you know that we have just queued up the patch titled

    Subject: memcg: avoid oom-killing innocent task in case of use_hierarchy

to the 2.6.31-stable tree.  Its filename is

    memcg-avoid-oom-killing-innocent-task-in-case-of-use_hierarchy.patch

A git repo of this tree can be found at 
    http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

  parent reply	other threads:[~2010-01-05 19:33 UTC|newest]

Thread overview: 39+ 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  5:57 ` Daisuke Nishimura
2009-11-24  7:28 ` [BUGFIX][PATCH -stable] " Daisuke Nishimura
2009-11-24  7:28   ` Daisuke Nishimura
2009-11-25  0:00   ` KAMEZAWA Hiroyuki
2009-11-25  0:00     ` KAMEZAWA Hiroyuki
2009-11-25  5:32     ` [BUGFIX][PATCH v2 " Daisuke Nishimura
2009-11-25  5:32       ` Daisuke Nishimura
2009-11-25  5:50       ` KAMEZAWA Hiroyuki
2009-11-25  5:50         ` KAMEZAWA Hiroyuki
2009-11-25 20:45       ` Andrew Morton
2009-11-25 20:45         ` Andrew Morton
2009-11-26  0:11         ` [BUGFIX][PATCH v2 -mmotm] " Daisuke Nishimura
2009-11-26  0:11           ` Daisuke Nishimura
2009-12-17  0:47       ` [BUGFIX][PATCH v2 -stable] " Daisuke Nishimura
2009-12-17  0:47         ` Daisuke Nishimura
2010-01-04 22:28         ` [stable] " Greg KH
2010-01-04 22:28           ` Greg KH
2010-01-05  3:26           ` [stable][BUGFIX][PATCH v3] " Daisuke Nishimura
2010-01-05  3:26             ` Daisuke Nishimura
2010-01-05 19:26             ` [stable] [BUGFIX][PATCH " Greg KH
2010-01-05 19:26               ` Greg KH
2010-01-05 19:33             ` gregkh [this message]
2009-11-25  4:08   ` [BUGFIX][PATCH -stable] " Balbir Singh
2009-11-25  4:08     ` Balbir Singh
2009-11-24 13:31 ` [BUGFIX][PATCH -mmotm] " Balbir Singh
2009-11-24 13:31   ` Balbir Singh
2009-11-24 14:00   ` Daisuke Nishimura
2009-11-24 14:00     ` Daisuke Nishimura
2009-11-24 17:04     ` Balbir Singh
2009-11-24 17:04       ` Balbir Singh
2009-11-24 23:49       ` Daisuke Nishimura
2009-11-24 23:49         ` Daisuke Nishimura
2009-11-25  3:29         ` Balbir Singh
2009-11-25  3:29           ` Balbir Singh
2009-11-25  0:07       ` KAMEZAWA Hiroyuki
2009-11-25  0:07         ` KAMEZAWA Hiroyuki
2009-11-25  4:09 ` Balbir Singh
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=12627199842369@kroah.org \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=d-nishimura@mtf.biglobe.ne.jp \
    --cc=greg@kroah.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=nishimura@mxp.nes.nec.co.jp \
    --cc=rientjes@google.com \
    --cc=stable-commits@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.