linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Julius Hemanth Pitti (jpitti)" <jpitti@cisco.com>
To: "greg@kroah.com" <greg@kroah.com>
Cc: "vdavydov.dev@gmail.com" <vdavydov.dev@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"xlpang@linux.alibaba.com" <xlpang@linux.alibaba.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"xe-linux-external(mailer list)" <xe-linux-external@cisco.com>,
	"mhocko@suse.com" <mhocko@suse.com>,
	"ktkhai@virtuozzo.com" <ktkhai@virtuozzo.com>
Subject: Re: [PATCH stable v5.8] mm: memcg: fix memcg reclaim soft lockup
Date: Mon, 21 Sep 2020 16:15:51 +0000	[thread overview]
Message-ID: <9dd7b7a8225a90019f74eb303b1f269d85628e94.camel@cisco.com> (raw)
In-Reply-To: <20200921161205.GC1096614@kroah.com>

On Mon, 2020-09-21 at 18:12 +0200, Greg KH wrote:
> On Thu, Sep 17, 2020 at 06:19:13PM -0700, Julius Hemanth Pitti wrote:
> > From: Xunlei Pang <xlpang@linux.alibaba.com>
> > 
> > commit e3336cab2579012b1e72b5265adf98e2d6e244ad upstream.
> > 
> > We've met softlockup with "CONFIG_PREEMPT_NONE=y", when the target
> > memcg
> > doesn't have any reclaimable memory.
> > 
> > It can be easily reproduced as below:
> > 
> >   watchdog: BUG: soft lockup - CPU#0 stuck for
> > 111s![memcg_test:2204]
> >   CPU: 0 PID: 2204 Comm: memcg_test Not tainted 5.9.0-rc2+ #12
> >   Call Trace:
> >     shrink_lruvec+0x49f/0x640
> >     shrink_node+0x2a6/0x6f0
> >     do_try_to_free_pages+0xe9/0x3e0
> >     try_to_free_mem_cgroup_pages+0xef/0x1f0
> >     try_charge+0x2c1/0x750
> >     mem_cgroup_charge+0xd7/0x240
> >     __add_to_page_cache_locked+0x2fd/0x370
> >     add_to_page_cache_lru+0x4a/0xc0
> >     pagecache_get_page+0x10b/0x2f0
> >     filemap_fault+0x661/0xad0
> >     ext4_filemap_fault+0x2c/0x40
> >     __do_fault+0x4d/0xf9
> >     handle_mm_fault+0x1080/0x1790
> > 
> > It only happens on our 1-vcpu instances, because there's no chance
> > for
> > oom reaper to run to reclaim the to-be-killed process.
> > 
> > Add a cond_resched() at the upper shrink_node_memcgs() to solve
> > this
> > issue, this will mean that we will get a scheduling point for each
> > memcg
> > in the reclaimed hierarchy without any dependency on the
> > reclaimable
> > memory in that memcg thus making it more predictable.
> > 
> > Suggested-by: Michal Hocko <mhocko@suse.com>
> > Signed-off-by: Xunlei Pang <xlpang@linux.alibaba.com>
> > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> > Acked-by: Chris Down <chris@chrisdown.name>
> > Acked-by: Michal Hocko <mhocko@suse.com>
> > Acked-by: Johannes Weiner <hannes@cmpxchg.org>
> > Link: 
> > http://lkml.kernel.org/r/1598495549-67324-1-git-send-email-xlpang@linux.alibaba.com
> > Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
> > Fixes: b0dedc49a2da ("mm/vmscan.c: iterate only over charged
> > shrinkers during memcg shrink_slab()")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Julius Hemanth Pitti <jpitti@cisco.com>
> > ---
> >  mm/vmscan.c | 8 ++++++++
> >  1 file changed, 8 insertions(+)
> 
> The Fixes: tag you show here goes back to 4.19, can you provide a
> 4.19.y
> and 5.4.y version of this as well?
Sure. Will send for both 5.4.y and 4.19.y.

> 
> thanks,
> 
> greg k-h

      reply	other threads:[~2020-09-21 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18  1:19 Julius Hemanth Pitti
2020-09-21 16:12 ` Greg KH
2020-09-21 16:15   ` Julius Hemanth Pitti (jpitti) [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=9dd7b7a8225a90019f74eb303b1f269d85628e94.camel@cisco.com \
    --to=jpitti@cisco.com \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=hannes@cmpxchg.org \
    --cc=ktkhai@virtuozzo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vdavydov.dev@gmail.com \
    --cc=xe-linux-external@cisco.com \
    --cc=xlpang@linux.alibaba.com \
    /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