From: Uladzislau Rezki <urezki@gmail.com>
To: chenyichong <chenyichong@uniontech.com>
Cc: wangqing7171@gmail.com, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzbot+37b7f6cd519f7fb8d32a@syzkaller.appspotmail.com,
urezki@gmail.com
Subject: Re: [PATCH] mm/vmalloc: fix KMSAN uninit in decay_va_pool_node list handling
Date: Fri, 3 Apr 2026 12:55:31 +0200 [thread overview]
Message-ID: <ac-coy4uxcDQGkBT@pc636> (raw)
In-Reply-To: <B7281353F876D424+20260403075204.894243-1-chenyichong@uniontech.com>
On Fri, Apr 03, 2026 at 03:52:03PM +0800, chenyichong wrote:
> Prevent decay_va_pool_node from overwriting concurrent repopulation of
> vmap_node pool[i].head while purging. Read/reset pool[i].len under
> pool_lock and splice leftover vmap_area nodes back into the pool
> instead of replacing the list.
>
> Reported-by: syzbot+37b7f6cd519f7fb8d32a@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=37b7f6cd519f7fb8d32a
> Fixes: 7679ba6b36db ("mm: vmalloc: add a shrinker to drain vmap pools")
> Signed-off-by: chenyichong <chenyichong@uniontech.com>
> ---
> mm/vmalloc.c | 13 +++++++++----
> 1 file changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index ecbac900c35f..72fb60553a71 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -2233,10 +2233,9 @@ decay_va_pool_node(struct vmap_node *vn, bool full_decay)
> /* Detach the pool, so no-one can access it. */
> spin_lock(&vn->pool_lock);
> list_replace_init(&vn->pool[i].head, &tmp_list);
> - spin_unlock(&vn->pool_lock);
> -
> pool_len = n_decay = vn->pool[i].len;
> WRITE_ONCE(vn->pool[i].len, 0);
> + spin_unlock(&vn->pool_lock);
>
> /* Decay a pool by ~25% out of left objects. */
> if (!full_decay)
> @@ -2259,8 +2258,14 @@ decay_va_pool_node(struct vmap_node *vn, bool full_decay)
> */
> if (!list_empty(&tmp_list)) {
> spin_lock(&vn->pool_lock);
> - list_replace_init(&tmp_list, &vn->pool[i].head);
> - WRITE_ONCE(vn->pool[i].len, pool_len);
> + /*
> + * Merge leftover areas back into the pool rather than
> + * replacing the whole list. A concurrent allocator can
> + * repopulate vn->pool[i].head while we are decaying
> + * tmp_list, and replacing would drop those nodes.
> + */
> + list_splice_tail_init(&tmp_list, &vn->pool[i].head);
> + WRITE_ONCE(vn->pool[i].len, vn->pool[i].len + pool_len);
>
"A concurrent allocator can repopulate..." - Where is it done? Probably
you meant something different.
--
Uladzislau Rezki
next prev parent reply other threads:[~2026-04-03 10:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 8:14 [PATCH] mm/vmalloc: fix KMSAN uninit-value warning in decay_va_pool_node() Qing Wang
2026-04-02 10:31 ` Uladzislau Rezki
2026-04-02 15:45 ` Uladzislau Rezki
2026-04-03 2:56 ` Qing Wang
2026-04-03 3:30 ` Morduan Zang
2026-04-03 3:50 ` Qing Wang
2026-04-03 3:14 ` Qing Wang
2026-04-03 7:52 ` [PATCH] mm/vmalloc: fix KMSAN uninit in decay_va_pool_node list handling chenyichong
2026-04-03 10:55 ` Uladzislau Rezki [this message]
2026-04-03 17:22 ` Uladzislau Rezki
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=ac-coy4uxcDQGkBT@pc636 \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chenyichong@uniontech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+37b7f6cd519f7fb8d32a@syzkaller.appspotmail.com \
--cc=wangqing7171@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