From: Vlastimil Babka <vbabka@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
patches@lists.linux.dev,
Roman Gushchin <roman.gushchin@linux.dev>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
Chengming Zhou <chengming.zhou@linux.dev>
Subject: [GIT PULL] slab fixes for 6.9-rc7
Date: Mon, 6 May 2024 12:03:11 +0200 [thread overview]
Message-ID: <eea90337-bea4-444b-8f92-576ee242a497@suse.cz> (raw)
Hi Linus,
please pull the latest slab hot-fixes from:
git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git tags/slab-for-6.9-rc7-fixes
Thanks,
Vlastimil
======================================
- Fix for cleanup infrastructure (Dan Carpenter)
This makes the __free(kfree) cleanup hooks not crash on error pointers.
- SLUB fix for freepointer checking (Nicolas Bouchinet)
This fixes a recently introduced bug that manifests when init_on_free,
CONFIG_SLAB_FREELIST_HARDENED and consistency checks (slub_debug=F) are
all enabled, and results in false-positive freepointer corrupt reports
for caches that store freepointer outside of the object area.
----------------------------------------------------------------
Dan Carpenter (1):
mm/slab: make __free(kfree) accept error pointers
Nicolas Bouchinet (1):
mm/slub: avoid zeroing outside-object freepointer for single free
include/linux/slab.h | 4 ++--
mm/slub.c | 52 +++++++++++++++++++++++++++++-----------------------
2 files changed, 31 insertions(+), 25 deletions(-)
next reply other threads:[~2024-05-06 10:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 10:03 Vlastimil Babka [this message]
2024-05-06 17:45 ` [GIT PULL] slab fixes for 6.9-rc7 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=eea90337-bea4-444b-8f92-576ee242a497@suse.cz \
--to=vbabka@suse.cz \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=patches@lists.linux.dev \
--cc=penberg@kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).