From: Vlastimil Babka <vbabka@suse.cz>
To: Muchun Song <songmuchun@bytedance.com>, akpm@linux-foundation.org
Cc: hannes@cmpxchg.org, muchun.song@linux.dev, nphamcs@gmail.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Shakeel Butt <shakeel.butt@linux.dev>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] mm: list_lru: fix UAF for memory cgroup
Date: Thu, 1 Aug 2024 10:06:37 +0200 [thread overview]
Message-ID: <319812ce-a15f-4004-a166-d281b8525616@suse.cz> (raw)
In-Reply-To: <20240801024603.1865-1-songmuchun@bytedance.com>
On 8/1/24 04:46, 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.
>
> Fixes: 0a97c01cd20b ("list_lru: allow explicit memcg and NUMA node selection")
> Signed-off-by: Muchun Song <songmuchun@bytedance.com>
> Acked-by: Shakeel Butt <shakeel.butt@linux.dev>
> Cc: <stable@vger.kernel.org>
Acked-by: Vlastimil Babka <vbabka@suse.cz>
> ---
> v2:
> Only grab rcu lock when necessary (Vlastimil Babka)
>
> mm/list_lru.c | 28 ++++++++++++++++++++++------
> 1 file changed, 22 insertions(+), 6 deletions(-)
>
> diff --git a/mm/list_lru.c b/mm/list_lru.c
> index a29d96929d7c7..9b7ff06e9d326 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 */
>
> +/* 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,22 @@ 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;
>
> - return list_lru_add(lru, item, nid, memcg);
> + if (list_lru_memcg_aware(lru)) {
> + rcu_read_lock();
> + ret = list_lru_add(lru, item, nid, mem_cgroup_from_slab_obj(item));
> + rcu_read_unlock();
> + } else {
> + ret = list_lru_add(lru, item, nid, NULL);
> + }
> +
> + 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 +148,18 @@ 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;
>
> - return list_lru_del(lru, item, nid, memcg);
> + if (list_lru_memcg_aware(lru)) {
> + rcu_read_lock();
> + ret = list_lru_del(lru, item, nid, mem_cgroup_from_slab_obj(item));
> + rcu_read_unlock();
> + } else {
> + ret = list_lru_del(lru, item, nid, NULL);
> + }
> +
> + return ret;
> }
> EXPORT_SYMBOL_GPL(list_lru_del_obj);
>
prev parent reply other threads:[~2024-08-01 8:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 2:46 Muchun Song
2024-08-01 8:06 ` Vlastimil Babka [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=319812ce-a15f-4004-a166-d281b8525616@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=nphamcs@gmail.com \
--cc=shakeel.butt@linux.dev \
--cc=songmuchun@bytedance.com \
--cc=stable@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