From: Corey Minyard <corey@minyard.net>
To: Breno Leitao <leitao@debian.org>
Cc: Rik van Riel <riel@surriel.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
openipmi-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH] ipmi: fix suspicious RCU usage warning
Date: Mon, 17 Mar 2025 07:27:30 -0500 [thread overview]
Message-ID: <Z9gVMuEMk9yNNL89@mail.minyard.net> (raw)
In-Reply-To: <20250317-horned-nano-degu-a6e5bc@leitao>
On Mon, Mar 17, 2025 at 02:33:31AM -0700, Breno Leitao wrote:
> On Wed, Mar 12, 2025 at 01:19:32PM -0400, Rik van Riel wrote:
> > On recent kernels this warning fires:
> >
> > drivers/char/ipmi/ipmi_msghandler.c:1238 RCU-list traversed in non-reader section!!
> >
> > This looks like a fairly simple lockdep trigger, where
> > list_for_each_entry_rcu and list_for_each_entry_srcu are
> > functionally identical, but the lockdep annotation in
> > the former has an extra check.
> >
> > That extra check is whether the RCU read lock is held,
> > which is not true when the code uses srcu_read_lock.
> >
> > Get rid of the warning by using the properly annotated
> > list traversal macro.
>
> Thanks for looking at this one.
>
> There was a discussion about this issue a few years ago, with
> a different approach that never landed upstream.
>
> https://lore.kernel.org/all/20201119123831.GH3710@minyard.net/#r
I thought this looked familiar.
Breno, I believe you suggested a change to the patch that sounded
reasonable, so I removed the patch, and then nothing happened and I
didn't follow up.
This is kind of a mess :-(. Let me look at it.
-corey
next prev parent reply other threads:[~2025-03-17 12:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 17:19 Rik van Riel
2025-03-12 17:29 ` Paul E. McKenney
2025-03-12 18:35 ` Paolo Bonzini
2025-03-13 19:04 ` kernel test robot
2025-03-17 9:33 ` Breno Leitao
2025-03-17 12:27 ` Corey Minyard [this message]
2025-04-16 13:18 ` Corey Minyard
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=Z9gVMuEMk9yNNL89@mail.minyard.net \
--to=corey@minyard.net \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=paulmck@kernel.org \
--cc=riel@surriel.com \
/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
all inboxes | Powered by JetHome®