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>, Hao Li <hao.li@linux.dev>,
Alexei Starovoitov <ast@kernel.org>
Subject: [GIT PULL] slab updates for 7.0 part 2
Date: Mon, 16 Feb 2026 17:50:51 +0100 [thread overview]
Message-ID: <0c8f9910-1b4f-4a8c-846e-397f328662ae@suse.cz> (raw)
Hi Linus,
please pull the latest slab updates from:
git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git tags/slab-for-7.0-part2
There are two stable fixes for kmalloc_nolock() corner cases. The other two
patches are lifting a significant limitation of kmalloc_nolock() so that
kfree_rcu() can be used with it, and will allow bpf to start using this [1].
However they only went to -next a week ago so I want to be clear about it,
as I know it should have been there earlier for a non-strictly-fix changes.
[1] https://lore.kernel.org/all/CAADnVQ%2Bq3QPqNdV3MuysQJQgxSS4g6CV%2BVzN2%3DUqCPHw7xq%3DSQ@mail.gmail.com/
Thanks,
Vlastimil
======================================
- Two stable fixes for kmalloc_nolock() usage from NMI context (Harry Yoo)
- Allow kmalloc_nolock() allocations to be freed with kfree() and thus
also kfree_rcu() and simplify slabobj_ext handling - we no longer need to
track how it was allocated to use the matching freeing function (Harry
Yoo)
----------------------------------------------------------------
The following changes since commit 815c8e35511d0b9a214e9f644983fe477af9d5cb:
Merge branch 'slab/for-7.0/sheaves' into slab/for-next (2026-02-10 09:10:00 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git tags/slab-for-7.0-part2
for you to fetch changes up to 27125df9a5d3b4cfd03bce3a8ec405a368cc9aae:
mm/slab: drop the OBJEXTS_NOSPIN_ALLOC flag from enum objext_flags (2026-02-10 11:39:30 +0100)
----------------------------------------------------------------
slab updates for 7.0 part2
----------------------------------------------------------------
Harry Yoo (4):
mm/slab: do not access current->mems_allowed_seq if !allow_spin
mm/slab: use prandom if !allow_spin
mm/slab: allow freeing kmalloc_nolock()'d objects using kfree[_rcu]()
mm/slab: drop the OBJEXTS_NOSPIN_ALLOC flag from enum objext_flags
include/linux/memcontrol.h | 3 +-
include/linux/rcupdate.h | 4 +--
mm/kmemleak.c | 22 ++++++-------
mm/slub.c | 80 ++++++++++++++++++++++++++++++++++++----------
4 files changed, 76 insertions(+), 33 deletions(-)
next reply other threads:[~2026-02-16 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 16:50 Vlastimil Babka [this message]
2026-02-16 22:11 ` 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=0c8f9910-1b4f-4a8c-846e-397f328662ae@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=ast@kernel.org \
--cc=cl@gentwo.org \
--cc=hao.li@linux.dev \
--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