linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Weiner <hannes@cmpxchg.org>
To: Michal Hocko <mhocko@suse.cz>
Cc: akpm@linux-foundation.org, mm-commits@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: + mm-memcg-use-proper-memcg-in-limit-bypass.patch added to -mm tree
Date: Thu, 31 Oct 2013 10:14:09 -0400	[thread overview]
Message-ID: <20131031141409.GD14054@cmpxchg.org> (raw)
In-Reply-To: <20131031083707.GA13144@dhcp22.suse.cz>

On Thu, Oct 31, 2013 at 09:37:07AM +0100, Michal Hocko wrote:
> On Wed 30-10-13 15:12:47, Andrew Morton wrote:
> > Subject: + mm-memcg-use-proper-memcg-in-limit-bypass.patch added to -mm tree
> > To: hannes@cmpxchg.org,mhocko@suse.cz
> > From: akpm@linux-foundation.org
> > Date: Wed, 30 Oct 2013 15:12:47 -0700
> > 
> > 
> > The patch titled
> >      Subject: mm: memcg: use proper memcg in limit bypass
> > has been added to the -mm tree.  Its filename is
> >      mm-memcg-use-proper-memcg-in-limit-bypass.patch
> > 
> > This patch should soon appear at
> >     http://ozlabs.org/~akpm/mmots/broken-out/mm-memcg-use-proper-memcg-in-limit-bypass.patch
> > and later at
> >     http://ozlabs.org/~akpm/mmotm/broken-out/mm-memcg-use-proper-memcg-in-limit-bypass.patch
> > 
> > Before you just go and hit "reply", please:
> >    a) Consider who else should be cc'ed
> >    b) Prefer to cc a suitable mailing list as well
> >    c) Ideally: find the original patch on the mailing list and do a
> >       reply-to-all to that, adding suitable additional cc's
> > 
> > *** Remember to use Documentation/SubmitChecklist when testing your code ***
> > 
> > The -mm tree is included into linux-next and is updated
> > there every 3-4 working days
> > 
> > ------------------------------------------------------
> > From: Johannes Weiner <hannes@cmpxchg.org>
> > Subject: mm: memcg: use proper memcg in limit bypass
> > 
> > 84235de ("fs: buffer: move allocation failure loop into the allocator")
> > allowed __GFP_NOFAIL allocations to bypass the limit if they fail to
> > reclaim enough memory for the charge.  Because the main test case was on a
> > 3.2-based system, this patch missed the fact that on newer kernels the
> > charge function needs to return root_mem_cgroup when bypassing the limit,
> > and not NULL.  This will corrupt whatever memory is at NULL + percpu
> > pointer offset.  Fix this quickly before problems are reported.
> > 
> > Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
> > Cc: Michal Hocko <mhocko@suse.cz>
> > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> 
> Acked-by: Michal Hocko <mhocko@suse.cz>
> 
> I guess this should be marked for stable as 84235de has been marked so.
> It would be also nice to mention that bypass with root_mem_cgroup
> happened at 3.3 times (it was done by 38c5d72f3ebe5 AFAICS).

I recalled the stable tag for the other patch, will send the full
series to stable once those patches have been in a release for some
time.

--
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>

      reply	other threads:[~2013-11-01 14:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5271845f.Z9YgMQjBJAhXMdBZ%akpm@linux-foundation.org>
2013-10-31  8:37 ` Michal Hocko
2013-10-31 14:14   ` Johannes Weiner [this message]

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=20131031141409.GD14054@cmpxchg.org \
    --to=hannes@cmpxchg.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    --cc=mm-commits@vger.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