From: ThangNN99 <ngocthang2710.1999@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-rt-devel@lists.linux.dev, linux-mm@kvack.org,
Vlastimil Babka <vbabka@kernel.org>, Harry Yoo <harry@kernel.org>
Subject: Re: [PATCH v2] mm/slab: don't use kfree_rcu sheaves on PREEMPT_RT in kvfree_call_rcu()
Date: Mon, 31 Aug 2026 13:33:44 +0700 [thread overview]
Message-ID: <20260831063344.7933-1-ngocthang2710.1999@gmail.com> (raw)
In-Reply-To: <20260831062054.319EA1F000E9@smtp.kernel.org>
Thanks, both flagged items are pre-existing and out of scope for this
patch:
- The headless kvfree_rcu(ptr) might_sleep()/synchronize_rcu() path is
never reached by the caller this patch fixes: set_cpus_allowed_force()
uses the headed two-argument kfree_rcu(ptr, rcu) form specifically to
avoid it (see its own comment), so it's unrelated to the sheaf-bypass
this patch adds.
- kfree_call_rcu_nolock() still hitting local_trylock(&s->cpu_sheaves->lock)
unconditionally is exactly what this patch's commit message already
calls out as unsafe under a raw spinlock. This patch intentionally
leaves kfree_call_rcu_nolock() untouched; fixing its 'any context'
guarantee belongs in a separate patch.
This patch stays scoped to the specific syzbot-reported splat in
kvfree_call_rcu(). Happy to look at the two pre-existing issues
separately if a maintainer wants a follow-up patch for either.
Thanks,
ThangNN99
next parent reply other threads:[~2026-08-31 6:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260831062054.319EA1F000E9@smtp.kernel.org>
2026-08-31 6:33 ` ThangNN99 [this message]
2026-08-31 5:38 [PATCH] mm/slab: don't use kfree_rcu sheaves on PREEMPT_RT in kvfree_call_rcu() ThangNN99
2026-08-31 6:06 ` [PATCH v2] " ThangNN99
2026-08-31 13:00 ` Sebastian Andrzej Siewior
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=20260831063344.7933-1-ngocthang2710.1999@gmail.com \
--to=ngocthang2710.1999@gmail.com \
--cc=harry@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=vbabka@kernel.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