From: Vlastimil Babka <vbabka@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Harry Yoo <harry.yoo@oracle.com>,
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>
Subject: [GIT PULL] slab fix for 6.19-rc8
Date: Fri, 6 Feb 2026 09:59:01 +0100 [thread overview]
Message-ID: <c5f2a4f2-8156-4c4a-9f28-0fe129893e2a@suse.cz> (raw)
Hi Linus,
please pull the slab fix from:
git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git tags/slab-for-6.19-rc8-fix
Thanks,
Vlastimil
======================================
- A stable fix for memory allocation profiling tag not being cleared when
aborting an allocation due to memcg charge failure (Hao Ge)
----------------------------------------------------------------
The following changes since commit 99a3e3a1cfc93b8fe318c0a3a5cfb01f1d4ad53c:
slab: fix kmalloc_nolock() context check for PREEMPT_RT (2026-01-21 11:34:18 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git tags/slab-for-6.19-rc8-fix
for you to fetch changes up to e6c53ead2d8fa73206e0a63e9cd9aea6bc929837:
mm/slab: Add alloc_tagging_slab_free_hook for memcg_alloc_abort_single (2026-02-06 09:51:08 +0100)
----------------------------------------------------------------
slab fix for 6.19-rc8
----------------------------------------------------------------
Hao Ge (1):
mm/slab: Add alloc_tagging_slab_free_hook for memcg_alloc_abort_single
mm/slub.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
next reply other threads:[~2026-02-06 8:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 8:59 Vlastimil Babka [this message]
2026-02-06 23:09 ` 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=c5f2a4f2-8156-4c4a-9f28-0fe129893e2a@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--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=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