mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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>,
	"Uladzislau Rezki (Sony)" <urezki@gmail.com>,
	Guenter Roeck <linux@roeck-us.net>
Subject: [GIT PULL] slab fixes for 6.12-rc1
Date: Fri, 4 Oct 2024 15:55:07 +0200	[thread overview]
Message-ID: <f26fdcde-b8fd-4d63-b113-d6d39ab3bf15@suse.cz> (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-6.12-rc1

Thanks,
Vlastimil

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

Fixes for issues introduced in 6.12-rc1: kobject memory leak, unsupressed
warning and possible lockup in new slub_kunit tests, misleading code in
kvfree_rcu_queue_batch().

----------------------------------------------------------------
Nilay Shroff (1):
      mm, slab: fix use of SLAB_SUPPORTS_SYSFS in kmem_cache_release()

Uladzislau Rezki (Sony) (1):
      rcu/kvfree: Refactor kvfree_rcu_queue_batch()

Vlastimil Babka (2):
      mm, slab: suppress warnings in test_leak_destroy kunit test
      slub/kunit: skip test_kfree_rcu when the slub kunit test is built-in

 kernel/rcu/tree.c |  9 +++++----
 lib/slub_kunit.c  | 18 ++++++++++++------
 mm/slab.h         |  8 +++++++-
 mm/slab_common.c  |  5 +++--
 mm/slub.c         |  5 +++--
 5 files changed, 30 insertions(+), 15 deletions(-)

             reply	other threads:[~2024-10-04 13:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-04 13:55 Vlastimil Babka [this message]
2024-10-04 19:17 ` 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=f26fdcde-b8fd-4d63-b113-d6d39ab3bf15@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=linux@roeck-us.net \
    --cc=rientjes@google.com \
    --cc=roman.gushchin@linux.dev \
    --cc=torvalds@linux-foundation.org \
    --cc=urezki@gmail.com \
    /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®