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>,
	Suren Baghdasaryan <surenb@google.com>,
	Shakeel Butt <shakeel.butt@linux.dev>
Subject: [GIT PULL] slab fixes for 7.2-rc4
Date: Fri, 24 Jul 2026 14:32:13 +0200	[thread overview]
Message-ID: <abd000de-e6d6-492c-b50f-09d1309afc83@kernel.org> (raw)

Hi Linus,

please pull the latest slab fixes from:

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

Thanks,
Vlastimil

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

- Prevent unbounded recursion in free path with memory allocation profiling,
  which has caused a stack overflow on a Meta production host due to a
  125-deep __free_slab<->kfree recursion. (Harry Yoo)

- Fix type-based partitioning confusing sparse which does not know
  __builtin_infer_alloc_token() (Marco Elver)

- Fix a potential memory leak in bulk freeing path on NUMA machines.
  (Shengming Hu)
  
----------------------------------------------------------------
The following changes since commit dc59e4fea9d83f03bad6bddf3fa2e52491777482:

  Linux 7.2-rc1 (2026-06-28 12:01:31 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 5ff172f6c94d282d83cb88bdfec5f647ad9c6105:

  slab: silence sparse warning with type-based partitioning (2026-07-21 11:28:21 +0200)

----------------------------------------------------------------
slab fixes for 7.2-rc4

----------------------------------------------------------------
Harry Yoo (Oracle) (4):
      mm/slab: fix a memory leak due to bootstrapping sheaves twice
      mm/slab: decouple SLAB_NO_SHEAVES from SLAB_NO_OBJ_EXT
      lib/alloc_tag: introduce mem_alloc_profiling_permanently_disabled()
      mm/slab: prevent unbounded recursion in free path with new kmalloc type

Marco Elver (1):
      slab: silence sparse warning with type-based partitioning

Shengming Hu (1):
      mm/slub: fix lost local objects when bulk remote free batch fills

 include/linux/alloc_tag.h |   3 ++
 include/linux/slab.h      |  25 ++++++++--
 lib/alloc_tag.c           |   9 ++++
 mm/slab.h                 |  32 ++++++++++--
 mm/slab_common.c          |  19 +++++++-
 mm/slub.c                 | 121 +++++++++++++++++++---------------------------
 6 files changed, 131 insertions(+), 78 deletions(-)

             reply	other threads:[~2026-07-24 12:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24 12:32 Vlastimil Babka (SUSE) [this message]
2026-07-24 19:22 ` 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=abd000de-e6d6-492c-b50f-09d1309afc83@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=shakeel.butt@linux.dev \
    --cc=surenb@google.com \
    --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®