From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Harry Yoo <harry.yoo@oracle.com>, Hao Li <hao.li@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
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 fixes for 7.1-rc1
Date: Sun, 3 May 2026 10:35:47 +0200 [thread overview]
Message-ID: <38238703-4460-4a57-8d00-5e390fd2d4b5@kernel.org> (raw)
Hi Linus,
please pull the latest slab fixes from:
git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git tags/slab-for-7.1-rc1
Thanks,
Vlastimil
======================================
- Stable fixes for CONFIG_SMP=n where _nolock() allocations in NMI both at
kmalloc and page allocator levels are not properly protected by the
spin_trylock() semantics on !SMP. (Harry Yoo)
----------------------------------------------------------------
The following changes since commit 082a6d03a2d685a83a332666b500ad3966349588:
slub: fix data loss and overflow in krealloc() (2026-04-17 11:07:48 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git tags/slab-for-7.1-rc1
for you to fetch changes up to 5b31044e649e3e54c2caef135c09b371c2fbcd08:
mm/slab: return NULL early from kmalloc_nolock() in NMI on UP (2026-04-27 09:14:36 +0200)
----------------------------------------------------------------
slab fixes for 7.1-rc1
----------------------------------------------------------------
Harry Yoo (Oracle) (2):
mm/page_alloc: return NULL early from alloc_frozen_pages_nolock() in NMI on UP
mm/slab: return NULL early from kmalloc_nolock() in NMI on UP
mm/page_alloc.c | 5 +++++
mm/slub.c | 4 ++++
2 files changed, 9 insertions(+)
next reply other threads:[~2026-05-03 8:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-03 8:35 Vlastimil Babka (SUSE) [this message]
2026-05-03 16:59 ` [GIT PULL] slab fixes for 7.1-rc1 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=38238703-4460-4a57-8d00-5e390fd2d4b5@kernel.org \
--to=vbabka@kernel.org \
--cc=akpm@linux-foundation.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