From: Michal Hocko <mhocko@kernel.org>
To: Jing Xia <jing.xia.mail@gmail.com>
Cc: hannes@cmpxchg.org, vdavydov.dev@gmail.com,
chunyan.zhang@unisoc.com, cgroups@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] mm: memcg: fix use after free in mem_cgroup_iter()
Date: Thu, 19 Jul 2018 12:43:45 +0200 [thread overview]
Message-ID: <20180719104345.GV7193@dhcp22.suse.cz> (raw)
In-Reply-To: <1531994807-25639-1-git-send-email-jing.xia@unisoc.com>
[CC Andrew]
On Thu 19-07-18 18:06:47, Jing Xia wrote:
> It was reported that a kernel crash happened in mem_cgroup_iter(),
> which can be triggered if the legacy cgroup-v1 non-hierarchical
> mode is used.
>
> Unable to handle kernel paging request at virtual address 6b6b6b6b6b6b8f
> ......
> Call trace:
> mem_cgroup_iter+0x2e0/0x6d4
> shrink_zone+0x8c/0x324
> balance_pgdat+0x450/0x640
> kswapd+0x130/0x4b8
> kthread+0xe8/0xfc
> ret_from_fork+0x10/0x20
>
> mem_cgroup_iter():
> ......
> if (css_tryget(css)) <-- crash here
> break;
> ......
>
> The crashing reason is that mem_cgroup_iter() uses the memcg object
> whose pointer is stored in iter->position, which has been freed before
> and filled with POISON_FREE(0x6b).
>
> And the root cause of the use-after-free issue is that
> invalidate_reclaim_iterators() fails to reset the value of
> iter->position to NULL when the css of the memcg is released in non-
> hierarchical mode.
Well, spotted!
I suspect
Fixes: 6df38689e0e9 ("mm: memcontrol: fix possible memcg leak due to interrupted reclaim")
but maybe it goes further into past. I also suggest
Cc: stable
even though the non-hierarchical mode is strongly discouraged. A lack of
reports for 3 years is encouraging that not many people really use this
mode.
> Signed-off-by: Jing Xia <jing.xia.mail@gmail.com>
Acked-by: Michal Hocko <mhocko@suse.com>
Thanks!
> ---
> mm/memcontrol.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index e6f0d5e..8c0280b 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -850,7 +850,7 @@ static void invalidate_reclaim_iterators(struct mem_cgroup *dead_memcg)
> int nid;
> int i;
>
> - while ((memcg = parent_mem_cgroup(memcg))) {
> + for (; memcg; memcg = parent_mem_cgroup(memcg)) {
> for_each_node(nid) {
> mz = mem_cgroup_nodeinfo(memcg, nid);
> for (i = 0; i <= DEF_PRIORITY; i++) {
> --
> 1.9.1
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-07-19 10:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 10:06 [PATCH] mm: memcg: fix use after free in mem_cgroup_iter() Jing Xia
2018-07-19 10:43 ` Michal Hocko [this message]
2018-07-19 16:23 ` Shakeel Butt
2018-07-23 6:44 ` Michal Hocko
2018-07-23 16:17 ` Shakeel Butt
2018-07-24 7:28 ` Michal Hocko
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=20180719104345.GV7193@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=chunyan.zhang@unisoc.com \
--cc=hannes@cmpxchg.org \
--cc=jing.xia.mail@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).