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>
Subject: [GIT PULL] slab updates for 6.3-rc1
Date: Tue, 21 Feb 2023 15:33:02 +0100 [thread overview]
Message-ID: <0d7dde0e-ac9d-620a-cfe8-7897ed53be60@suse.cz> (raw)
Linus,
please pull the latest slab updates from:
git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git tags/slab-for-6.3
This time it's just a bunch of smaller cleanups and fixes for SLAB and SLUB:
- Make it possible to use kmem_cache_alloc_bulk() early in boot when
interrupts are not yet enabled, as code doing that started to appear via
new maple tree users (by Thomas Gleixner).
- Fix debugfs-related memory leak in SLUB (by Greg Kroah-Hartman).
- Use the standard idiom to get head page of folio (by SeongJae Park)
- Simplify and inline is_debug_pagealloc_cache() in SLAB (by lvqian)
- Remove unused variable in SLAB (by Gou Hao)
----------------------------------------------------------------
Gou Hao (1):
mm/slab: remove unused slab_early_init
Greg Kroah-Hartman (1):
mm/slub: fix memory leak with using debugfs_lookup()
SeongJae Park (1):
mm/sl{a,u}b: fix wrong usages of folio_page() for getting head pages
Thomas Gleixner (1):
mm, slab/slub: Ensure kmem_cache_alloc_bulk() is available early
Vlastimil Babka (2):
Merge branch 'slab/for-6.3/cleanups' into slab/for-linus
Merge branch 'slab/for-6.3/fixes' into slab/for-linus
lvqian (1):
mm/slab.c: cleanup is_debug_pagealloc_cache()
mm/slab.c | 34 +++++++++++++++-------------------
mm/slub.c | 13 +++++++------
2 files changed, 22 insertions(+), 25 deletions(-)
next reply other threads:[~2023-02-21 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 14:33 Vlastimil Babka [this message]
2023-02-23 22:20 ` 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=0d7dde0e-ac9d-620a-cfe8-7897ed53be60@suse.cz \
--to=vbabka@suse.cz \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--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
all inboxes | Powered by JetHome®