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 fix for 6.0-rc7
Date: Thu, 22 Sep 2022 22:13:51 +0200 [thread overview]
Message-ID: <9c0abd9f-5976-31e2-8802-e40270ad0014@suse.cz> (raw)
Linus,
please pull the latest slab changes from
git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git tags/slab-for-6.0-rc7
======================================
- Fix a possible use-after-free in SLUB's kmem_cache removal, introduced in
this cycle, by Feng Tang.
- WQ_MEM_RECLAIM dependency fix for the workqueue-based cpu slab flushing
introduced in 5.15, by Maurizio Lombardi.
- Add missing KASAN hooks in two kmalloc entry paths, by Peter Collingbourne.
- A BUG_ON() removal in SLUB's kmem_cache creation when allocation fails (too
small to possibly happen in practice, syzbot used fault injection), by Chao
Yu.
Thanks,
Vlastimil
----------------------------------------------------------------
Chao Yu (1):
mm/slub: fix to return errno if kmalloc() fails
Feng Tang (1):
mm/slab_common: fix possible double free of kmem_cache
Maurizio Lombardi (1):
mm: slub: fix flush_cpu_slab()/__free_slab() invocations in task context.
Peter Collingbourne (1):
kasan: call kasan_malloc() from __kmalloc_*track_caller()
mm/slab_common.c | 5 ++++-
mm/slub.c | 18 ++++++++++++++++--
2 files changed, 20 insertions(+), 3 deletions(-)
next reply other threads:[~2022-09-22 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 20:13 Vlastimil Babka [this message]
2022-09-22 21:52 ` 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=9c0abd9f-5976-31e2-8802-e40270ad0014@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