From: Vlastimil Babka <vbabka@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Rientjes <rientjes@google.com>,
Christoph Lameter <cl@linux.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>
Subject: [GIT PULL] slab updates for 6.13
Date: Fri, 15 Nov 2024 15:22:30 +0100 [thread overview]
Message-ID: <03ec75a9-aade-4457-ac21-5649116afa98@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-6.13
One new feature and non-critical fixes (mostly related to debugging).
No conflicts to be expected, AFAIK.
Thanks,
Vlastimil
======================================
- Add new slab_strict_numa boot parameter to enforce per-object memory policies
on top of slab folio policies, for systems where saving cost of remote
accesses is more important than minimizing slab allocation overhead
(Christoph Lameter)
- krealloc() fixes for not violating __GFP_ZERO guarantees on krealloc() when
slub_debug (redzone and object tracking) is enabled (Feng Tang)
- Fix a memory leak in case sysfs registration fails for a slab cache, and also
no longer fail to create the cache in that case (Hyeonggon Yoo)
- Fix handling of detected consistency problems (due to buggy slab user) with
slub_debug enabled, so that it does not cause further list corruption bugs
(yuan.gao)
- Code cleanup and kerneldocs polishing (Zhen Lei, Vlastimil Babka)
----------------------------------------------------------------
Christoph Lameter (1):
SLUB: Add support for per object memory policies
Feng Tang (5):
mm/kasan: Don't store metadata inside kmalloc object when slub_debug_orig_size is on
mm/slub: Move krealloc() and related code to slub.c
mm/slub: Consider kfence case for get_orig_size()
mm/slub: Improve redzone check and zeroing for krealloc()
mm/slub, kunit: Add testcase for krealloc redzone and zeroing
Hyeonggon Yoo (1):
mm/slab: Allow cache creation to proceed even if sysfs registration fails
Vlastimil Babka (2):
mm, slab: add kerneldocs for common SLAB_ flags
Merge branch 'slab/for-6.13/features' into slab/for-next
Zhen Lei (1):
mm/slab: remove duplicate check in create_cache()
yuan.gao (1):
mm/slub: Avoid list corruption when removing a slab from the full list
Documentation/admin-guide/kernel-parameters.txt | 10 ++
Documentation/mm/slub.rst | 9 +
include/linux/slab.h | 60 ++++---
lib/slub_kunit.c | 42 +++++
mm/kasan/generic.c | 7 +-
mm/slab.h | 11 ++
mm/slab_common.c | 101 ++---------
mm/slub.c | 212 +++++++++++++++++++++---
8 files changed, 320 insertions(+), 132 deletions(-)
next reply other threads:[~2024-11-15 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 14:22 Vlastimil Babka [this message]
2024-11-16 15:32 ` Sasha Levin
2024-11-16 15:35 ` Sasha Levin
2024-11-16 20:43 ` Vlastimil Babka
2024-11-17 3:41 ` Sasha Levin
2024-11-17 12:56 ` Xiongwei Song
2024-11-17 21:01 ` Vlastimil Babka
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=03ec75a9-aade-4457-ac21-5649116afa98@suse.cz \
--to=vbabka@suse.cz \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.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