From: Muchun Song <muchun.song@linux.dev>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Muchun Song <songmuchun@bytedance.com>,
Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Nhat Pham <nphamcs@gmail.com>,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
shakeel.butt@linux.dev
Subject: Re: [PATCH] mm: list_lru: fix UAF for memory cgroup
Date: Tue, 23 Jul 2024 19:23:02 +0800 [thread overview]
Message-ID: <1E56E5B4-7003-4EF4-98F7-C1FC30B2DE1D@linux.dev> (raw)
In-Reply-To: <E0A7CC1A-B02C-4210-A1DF-0600E027D5D0@linux.dev>
> On Jul 18, 2024, at 19:20, Muchun Song <muchun.song@linux.dev> wrote:
>
>
>
>> On Jul 18, 2024, at 18:30, Vlastimil Babka <vbabka@suse.cz> wrote:
>>
>> On 7/18/24 10:36 AM, Muchun Song wrote:
>>> The mem_cgroup_from_slab_obj() is supposed to be called under rcu
>>> lock or cgroup_mutex or others which could prevent returned memcg
>>> from being freed. Fix it by adding missing rcu read lock.
>>
>> Was the UAF ever observed, or is this due to code review?
>
> Just code review.
>
> Thanks.
>
>> Should there be some lockdep_assert somwhere?
>>
>
> It’s a good option to improve this. Maybe mem_cgroup_from_slab_obj() is a good place.
I added it to obj_cgroup_memcg() [1]. And CC memory cgroup maintainers to this thread.
[1] https://lore.kernel.org/linux-mm/20859F67-A80C-4FD0-990C-40C70905E55B@linux.dev/T/
>
>>> Fixes: 0a97c01cd20bb ("list_lru: allow explicit memcg and NUMA node selection)
>>> Signed-off-by: Muchun Song <songmuchun@bytedance.com>
>>> ---
>>> mm/list_lru.c | 24 ++++++++++++++++++------
>>> 1 file changed, 18 insertions(+), 6 deletions(-)
>>>
>>> diff --git a/mm/list_lru.c b/mm/list_lru.c
>>> index 3fd64736bc458..225da0778a3be 100644
>>> --- a/mm/list_lru.c
>>> +++ b/mm/list_lru.c
>>> @@ -85,6 +85,7 @@ list_lru_from_memcg_idx(struct list_lru *lru, int nid, int idx)
>>> }
>>> #endif /* CONFIG_MEMCG_KMEM */
>>>
>>> +/* The caller must ensure the memcg lifetime. */
>>> bool list_lru_add(struct list_lru *lru, struct list_head *item, int nid,
>>> struct mem_cgroup *memcg)
>>> {
>>> @@ -109,14 +110,20 @@ EXPORT_SYMBOL_GPL(list_lru_add);
>>>
>>> bool list_lru_add_obj(struct list_lru *lru, struct list_head *item)
>>> {
>>> + bool ret;
>>> int nid = page_to_nid(virt_to_page(item));
>>> - struct mem_cgroup *memcg = list_lru_memcg_aware(lru) ?
>>> - mem_cgroup_from_slab_obj(item) : NULL;
>>> + struct mem_cgroup *memcg;
>>>
>>> - return list_lru_add(lru, item, nid, memcg);
>>> + rcu_read_lock();
>>> + memcg = list_lru_memcg_aware(lru) ? mem_cgroup_from_slab_obj(item) : NULL;
>>> + ret = list_lru_add(lru, item, nid, memcg);
>>> + rcu_read_unlock();
>>> +
>>> + return ret;
>>> }
>>> EXPORT_SYMBOL_GPL(list_lru_add_obj);
>>>
>>> +/* The caller must ensure the memcg lifetime. */
>>> bool list_lru_del(struct list_lru *lru, struct list_head *item, int nid,
>>> struct mem_cgroup *memcg)
>>> {
>>> @@ -139,11 +146,16 @@ EXPORT_SYMBOL_GPL(list_lru_del);
>>>
>>> bool list_lru_del_obj(struct list_lru *lru, struct list_head *item)
>>> {
>>> + bool ret;
>>> int nid = page_to_nid(virt_to_page(item));
>>> - struct mem_cgroup *memcg = list_lru_memcg_aware(lru) ?
>>> - mem_cgroup_from_slab_obj(item) : NULL;
>>> + struct mem_cgroup *memcg;
>>>
>>> - return list_lru_del(lru, item, nid, memcg);
>>> + rcu_read_lock();
>>> + memcg = list_lru_memcg_aware(lru) ? mem_cgroup_from_slab_obj(item) : NULL;
>>> + ret = list_lru_del(lru, item, nid, memcg);
>>> + rcu_read_unlock();
>>> +
>>> + return ret;
>>> }
>>> EXPORT_SYMBOL_GPL(list_lru_del_obj);
>>>
>>
next prev parent reply other threads:[~2024-07-23 11:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 8:36 Muchun Song
2024-07-18 10:30 ` Vlastimil Babka
2024-07-18 11:20 ` Muchun Song
2024-07-23 11:23 ` Muchun Song [this message]
2024-07-23 17:52 ` Shakeel Butt
2024-07-24 0:45 ` Andrew Morton
2024-07-24 2:23 ` Muchun Song
2024-07-31 10:06 ` Vlastimil Babka (SUSE)
2024-08-01 2:42 ` Muchun Song
2024-07-31 20:28 ` Andrew Morton
2024-08-01 2:42 ` Muchun Song
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=1E56E5B4-7003-4EF4-98F7-C1FC30B2DE1D@linux.dev \
--to=muchun.song@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=nphamcs@gmail.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=songmuchun@bytedance.com \
--cc=vbabka@suse.cz \
/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