From: Vlastimil Babka <vbabka@suse.cz>
To: Osama Abdelkader <osama.abdelkader@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@gentwo.org>,
David Rientjes <rientjes@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Harry Yoo <harry.yoo@oracle.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: syzbot+6e04171f00f33c0d62fb@syzkaller.appspotmail.com
Subject: Re: [PATCH] mm/slub: zero-initialize slab object extensions to fix KMSAN
Date: Wed, 4 Feb 2026 22:34:11 +0100 [thread overview]
Message-ID: <82dafb42-ca29-4ea7-9c1f-114c10443237@suse.cz> (raw)
In-Reply-To: <20260204195751.188219-1-osama.abdelkader@gmail.com>
On 2/4/26 20:57, Osama Abdelkader wrote:
> KMSAN reports uninitialized reads in __memcg_slab_free_hook
> when freeing sigqueue objects. Although kmalloc_nolock(__GFP_ZERO)
> and kcalloc_node normally zero memory, some allocation paths
> (fallbacks, early boot, reused slabs, or races) may leave objcg undefined.
>
> Explicitly memset the obj_exts array after allocation to guarantee no
> uninitialized reads in __memcg_slab_free_hook and preserve correct memcg
> accounting.
>
> Reported-by: syzbot+6e04171f00f33c0d62fb@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=6e04171f00f33c0d62fb
> Signed-off-by: Osama Abdelkader <osama.abdelkader@gmail.com>
> ---
> mm/slub.c | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/mm/slub.c b/mm/slub.c
> index f77b7407c51b..e66d17ee7fa8 100644
> --- a/mm/slub.c
> +++ b/mm/slub.c
> @@ -2123,7 +2123,17 @@ int alloc_slab_obj_exts(struct slab *slab, struct kmem_cache *s,
> vec = kcalloc_node(objects, sizeof(struct slabobj_ext), gfp,
> slab_nid(slab));
> }
> - if (!vec) {
> + /*
> + * Explicitly zero the obj_exts array to ensure KMSAN recognizes it
> + * as initialized. Although kmalloc_nolock and kcalloc_node normally
> + * zero memory, KMSAN may not track this initialization in all cases,
> + * especially during early boot or with certain allocation paths.
> + * This explicit memset ensures KMSAN sees the initialization and
> + * prevents uninitialized value warnings when accessing objcg fields.
> + */
This explanation makes no sense to me. The kcalloc or kmalloc with
__GFP_ZERO above has just cleared the object, and this is just clearing it
again. It didn't happen sometimes in the past where KMSAN wouldn't track this.
The bug must have a different explanation, such as getting an invalid
pointer to kmem_cache_free(). Too bad it doesn't report any details about
the address.
> + if (vec)
> + memset(vec, 0, objects * sizeof(*vec));
> + else {
> /*
> * Try to mark vectors which failed to allocate.
> * If this operation fails, there may be a racing process
prev parent reply other threads:[~2026-02-04 21:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 19:57 Osama Abdelkader
2026-02-04 21:34 ` 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=82dafb42-ca29-4ea7-9c1f-114c10443237@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=harry.yoo@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osama.abdelkader@gmail.com \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=syzbot+6e04171f00f33c0d62fb@syzkaller.appspotmail.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