From: Vlastimil Babka <vbabka@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Harry Yoo <harry.yoo@oracle.com>,
David Rientjes <rientjes@google.com>,
Christoph Lameter <cl@gentwo.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] slab fix for 6.19-rc2
Date: Fri, 19 Dec 2025 17:22:18 +0100 [thread overview]
Message-ID: <271c4413-2d6a-4dd9-9b31-714cfef3f28f@suse.cz> (raw)
Hi Linus,
please pull the slab fix from:
git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git tags/slab-for-6.19-rc2
Thanks,
Vlastimil
======================================
- A stable fix for a missing tag reset that can happen in kfree_nolock()
with KASAN+SLUB_TINY configs. (Deepanshu Kartikey)
----------------------------------------------------------------
The following changes since commit 0f35040de59371ad542b915d7b91176c9910dadc:
mm/slab: introduce kvfree_rcu_barrier_on_cache() for cache destruction (2025-12-07 18:09:54 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git tags/slab-for-6.19-rc2
for you to fetch changes up to 53ca00a19d345197a37a1bf552e8d1e7b091666c:
mm/slub: reset KASAN tag in defer_free() before accessing freed memory (2025-12-10 13:54:53 +0100)
----------------------------------------------------------------
Deepanshu Kartikey (1):
mm/slub: reset KASAN tag in defer_free() before accessing freed memory
mm/slub.c | 2 ++
1 file changed, 2 insertions(+)
next reply other threads:[~2025-12-19 16:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 16:22 Vlastimil Babka [this message]
2025-12-20 19:44 ` pr-tracker-bot
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=271c4413-2d6a-4dd9-9b31-714cfef3f28f@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=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=torvalds@linux-foundation.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