From: Yu-Hsiang Tseng <asas1asas200@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Jeff Johnson <jjohnson@kernel.org>,
ath12k@lists.infradead.org,
Baochen Qiang <baochen.qiang@oss.qualcomm.com>,
Rameshkumar Sundaram <rameshkumar.sundaram@oss.qualcomm.com>,
Kalle Valo <kvalo@kernel.org>,
Clark Williams <clrkwllms@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH v2] wifi: ath12k: fix false positive RCU warnings on PREEMPT_RT
Date: Thu, 23 Apr 2026 02:12:46 +0800 [thread overview]
Message-ID: <20260422181246.1944073-1-asas1asas200@gmail.com> (raw)
In-Reply-To: <20260422142325.Glnd_2Zc@linutronix.de>
On Wed, Apr 22, 2026 at 04:23:25PM +0200, Sebastian Andrzej Siewior wrote:
> As elaborated above, this is not PREEMPT_RT specific but preemptible
> TREE RCU.
You're right. Sent v3 that clarifies the scope (preemptible RCU in
general, not only PREEMPT_RT).
> If both this then use this then I guess something like
> lockdep_assert_in_rcu_read_lock()
> is what you look for.
Adopted in v3 - thanks for the pointer, it reads much cleaner than
RCU_LOCKDEP_WARN().
v3: https://lore.kernel.org/ath12k/20260422180814.1938317-1-asas1asas200@gmail.com/
Thanks,
Yu-Hsiang
next prev parent reply other threads:[~2026-04-22 18:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 16:10 [PATCH] wifi: ath12k: fix false positive RCU warning on PREEMPT_RT Yu-Hsiang Tseng
2026-04-21 2:24 ` Baochen Qiang
2026-04-21 17:25 ` [PATCH v2] wifi: ath12k: fix false positive RCU warnings " Yu-Hsiang Tseng
2026-04-21 17:32 ` Rameshkumar Sundaram
2026-04-21 21:27 ` Jeff Johnson
2026-04-22 13:33 ` Jeff Johnson
2026-04-22 18:29 ` 曾昱翔
2026-04-22 2:06 ` Baochen Qiang
2026-04-22 14:23 ` Sebastian Andrzej Siewior
2026-04-22 18:12 ` Yu-Hsiang Tseng [this message]
2026-04-21 17:37 ` [PATCH] wifi: ath12k: fix false positive RCU warning " Yu-Hsiang Tseng
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=20260422181246.1944073-1-asas1asas200@gmail.com \
--to=asas1asas200@gmail.com \
--cc=ath12k@lists.infradead.org \
--cc=baochen.qiang@oss.qualcomm.com \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=jjohnson@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=linux-wireless@vger.kernel.org \
--cc=rameshkumar.sundaram@oss.qualcomm.com \
--cc=rostedt@goodmis.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