mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 fix for 7.1-rc4
Date: Fri, 22 May 2026 11:53:39 +0200	[thread overview]
Message-ID: <56e3c93e-2840-43d2-8f41-b2e435e0fc29@kernel.org> (raw)

Hi Linus,

please pull the latest slab fix from:

  git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git tags/slab-for-7.1-rc4

Thanks,
Vlastimil

======================================

- Stable fix for a missing cpus_read_lock in one of the cpu sheaves flushing
  paths. (Qing Wang)

----------------------------------------------------------------
The following changes since commit 5b31044e649e3e54c2caef135c09b371c2fbcd08:

  mm/slab: return NULL early from kmalloc_nolock() in NMI on UP (2026-04-27 09:14:36 +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-rc4

for you to fetch changes up to 67ea9d353d0ba12bdbc9183ff568dead9e949b80:

  mm/slub: hold cpus_read_lock around flush_rcu_sheaves_on_cache() (2026-05-14 14:56:58 +0200)

----------------------------------------------------------------
slab fixes for 7.1-rc4

----------------------------------------------------------------
Qing Wang (1):
      mm/slub: hold cpus_read_lock around flush_rcu_sheaves_on_cache()

 mm/slab_common.c | 2 ++
 mm/slub.c        | 1 +
 2 files changed, 3 insertions(+)

             reply	other threads:[~2026-05-22  9:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-22  9:53 Vlastimil Babka (SUSE) [this message]
2026-05-22 14:26 ` 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=56e3c93e-2840-43d2-8f41-b2e435e0fc29@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

all inboxes | Powered by JetHome®