linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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>,
	Kees Cook <keescook@chromium.org>
Subject: [GIT PULL] slab fixes for 6.1-rc4
Date: Wed, 9 Nov 2022 15:48:10 +0100	[thread overview]
Message-ID: <87a751bc-34be-b96e-f157-9c841d153f52@suse.cz> (raw)

Linus,

please pull the latest slab fixes from:

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

Most are small fixups as described bellow, except the !CONFIG_TRACING commit
eb4940d4adf5 which would be otherwise done in the next merge window as part
of upcoming hardening changes. But we realized it can make the kmalloc waste
tracking introduced in this window inaccurate, so decided to go with it now.

Thanks, Vlastimil

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

* Remove !CONFIG_TRACING kmalloc() wrappers intended to save a function call,
  due to incompatilibity with recently introduced wasted space tracking and
  planned hardening changes.

* A tracing parameter regression fix, by Kees Cook.

* Two kernel-doc warning fixups, by Lukas Bulwahn and myself.
  
----------------------------------------------------------------
Kees Cook (1):
      mm/slab_common: Restore passing "caller" for tracing

Lukas Bulwahn (1):
      mm/slab_common: repair kernel-doc for __ksize()

Vlastimil Babka (2):
      mm/slab: remove !CONFIG_TRACING variants of kmalloc_[node_]trace()
      mm, slab: remove duplicate kernel-doc comment for ksize()

 include/linux/slab.h | 23 -----------------------
 mm/slab_common.c     | 24 ++++--------------------
 2 files changed, 4 insertions(+), 43 deletions(-)


             reply	other threads:[~2022-11-09 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 14:48 Vlastimil Babka [this message]
2022-11-09 21:43 ` 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=87a751bc-34be-b96e-f157-9c841d153f52@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=keescook@chromium.org \
    --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