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>,
Christoph Hellwig <hch@infradead.org>
Subject: [GIT PULL] slab fix for 6.18-rc7
Date: Thu, 20 Nov 2025 19:45:02 +0100 [thread overview]
Message-ID: <3f4ec3be-0725-43cc-a75b-72549ebdc5c9@suse.cz> (raw)
Hi Linus,
please pull the latest slab fixes (actually mempool specific this time,
which is under SLAB in MAINTAINERS now as well).
Thanks,
Vlastimil
======================================
* Fix mempool poisoning order>0 pages with CONFIG_HIGHMEM (Vlastimil Babka)
======================================
The following changes since commit cbcff934fa7deb670d9545a3aad4d07e8f1e4f3c:
mm/slub: fix memory leak in free_to_pcs_bulk() (2025-11-13 19:56:46 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git tags/slab-for-6.18-rc7
for you to fetch changes up to ec33b59542d96830e3c89845ff833cf7b25ef172:
mm/mempool: fix poisoning order>0 pages with HIGHMEM (2025-11-14 17:55:23 +0100)
----------------------------------------------------------------
slab fix for 6.18-rc7
----------------------------------------------------------------
Vlastimil Babka (1):
mm/mempool: fix poisoning order>0 pages with HIGHMEM
mm/mempool.c | 32 ++++++++++++++++++++++++++------
1 file changed, 26 insertions(+), 6 deletions(-)
next reply other threads:[~2025-11-20 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 18:45 Vlastimil Babka [this message]
2025-11-20 18:58 ` Linus Torvalds
2025-11-20 20:11 ` Matthew Wilcox
2025-11-20 21:37 ` Linus Torvalds
2025-11-20 21:55 ` Linus Torvalds
2025-11-20 19:00 ` 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=3f4ec3be-0725-43cc-a75b-72549ebdc5c9@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=harry.yoo@oracle.com \
--cc=hch@infradead.org \
--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