From: Tejun Heo <tj@kernel.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
cgroups@vger.kernel.org, linux-mm@kvack.org, kernel-team@fb.com
Subject: Re: [PATCH for-5.2-fixes] memcg: Don't loop on css_tryget_online() failure
Date: Wed, 5 Jun 2019 06:26:07 -0700 [thread overview]
Message-ID: <20190605132607.GI374014@devbig004.ftw2.facebook.com> (raw)
In-Reply-To: <20190605125520.GF15685@dhcp22.suse.cz>
On Wed, Jun 05, 2019 at 02:55:20PM +0200, Michal Hocko wrote:
> On Wed 29-05-19 14:06:17, Tejun Heo wrote:
> > A PF_EXITING task may stay associated with an offline css.
> > get_mem_cgroup_from_mm() may deadlock if mm->owner is in such state.
> > All similar logics in memcg are falling back to root memcg on
> > tryget_online failure and get_mem_cgroup_from_mm() can do the same.
> >
> > A similar failure existed for task_get_css() and could be triggered
> > through BSD process accounting racing against memcg offlining. See
> > 18fa84a2db0e ("cgroup: Use css_tryget() instead of css_tryget_online()
> > in task_get_css()") for details.
> >
> > Signed-off-by: Tejun Heo <tj@kernel.org>
>
> Do we need to mark this patch for stable or this is too unlikely to
> happen?
This one's a lot less likely than the one in task_get_css() which
already is pretty low frequency. I don't think it warrants -stable
tagging.
Thanks.
--
tejun
prev parent reply other threads:[~2019-06-05 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 21:06 [PATCH for-5.2-fixes] memcg: Don't loop on css_tryget_online() failure Tejun Heo
2019-06-05 12:55 ` Michal Hocko
2019-06-05 13:26 ` Tejun Heo [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=20190605132607.GI374014@devbig004.ftw2.facebook.com \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=vdavydov.dev@gmail.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