From: Rik van Riel <riel@surriel.com>
To: Corey Minyard <corey@minyard.net>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
openipmi-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: [PATCH] ipmi: fix suspicious RCU usage warning
Date: Wed, 12 Mar 2025 13:19:32 -0400 [thread overview]
Message-ID: <20250312131932.44d901f7@fangorn> (raw)
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.
Signed-off-by: Rik van Riel <riel@surriel.com>
---
drivers/char/ipmi/ipmi_msghandler.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/char/ipmi/ipmi_msghandler.c b/drivers/char/ipmi/ipmi_msghandler.c
index 1e5313748f8b..a2823763fd37 100644
--- a/drivers/char/ipmi/ipmi_msghandler.c
+++ b/drivers/char/ipmi/ipmi_msghandler.c
@@ -1235,7 +1235,7 @@ int ipmi_create_user(unsigned int if_num,
return -ENOMEM;
index = srcu_read_lock(&ipmi_interfaces_srcu);
- list_for_each_entry_rcu(intf, &ipmi_interfaces, link) {
+ list_for_each_entry_srcu(intf, &ipmi_interfaces, link) {
if (intf->intf_num == if_num)
goto found;
}
--
2.48.1
next reply other threads:[~2025-03-12 17:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 17:19 Rik van Riel [this message]
2025-03-12 17:29 ` [PATCH] ipmi: fix suspicious RCU usage warning 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
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=20250312131932.44d901f7@fangorn \
--to=riel@surriel.com \
--cc=corey@minyard.net \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=paulmck@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.