From: John Garry <john.garry@huawei.com>
To: Amol Grover <frextrite@gmail.com>,
Corey Minyard <minyard@acm.org>, "Arnd Bergmann" <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: <openipmi-developer@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>,
<linux-kernel-mentees@lists.linuxfoundation.org>,
Joel Fernandes <joel@joelfernandes.org>,
Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>,
"Paul E . Mckenney" <paulmck@kernel.org>
Subject: Re: [PATCH] ipmi: Fix RCU list lockdep debugging warnings
Date: Fri, 28 Feb 2020 11:49:01 +0000 [thread overview]
Message-ID: <b843fa9d-7fd3-940f-fb18-5ce3bef3a9be@huawei.com> (raw)
In-Reply-To: <20200228081731.18149-1-frextrite@gmail.com>
On 28/02/2020 08:17, Amol Grover wrote:
> It is completely safe to traverse ipmi_interfaces and
> intf->users under SRCU read lock using list_for_each_entry_rcu().
> Tell lockdep about it as well else it will show false-positive
> warnings as the one below.
>
> Fixes the following false-positive warning and others that may follow.
>
> [ 29.772408] =============================
> [ 29.776863] WARNING: suspicious RCU usage
> [ 29.780915] 5.6.0-rc3-00001-g907305ae6618-dirty #1755 Not tainted
> [ 29.787046] -----------------------------
> [ 29.791100] drivers/char/ipmi/ipmi_msghandler.c:744 RCU-list traversed in
> non-reader section!!
>
> Reported-by: John Garry <john.garry@huawei.com>
> Suggested-by: Paul E. McKenney <paulmck@kernel.org>
> Signed-off-by: Amol Grover <frextrite@gmail.com>
Tested-by: John Garry <john.garry@huawei.com>
Thanks, the warnings have gone away with this
> ---
> drivers/char/ipmi/ipmi_msghandler.c | 18 ++++++++++++------
> 1 file changed, 12 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/char/ipmi/ipmi_msghandler.c b/drivers/char/ipmi/ipmi_msghandler.c
> index cad9563f8f48..d202022c69de 100644
> --- a/drivers/char/ipmi/ipmi_msghandler.c
> +++ b/drivers/char/ipmi/ipmi_msghandler.c
> @@ -741,7 +741,8 @@ int ipmi_smi_watcher_register(struct ipmi_smi_watcher *watcher)
> list_add(&watcher->link, &smi_watchers);
>
> index = srcu_read_lock(&ipmi_interfaces_srcu);
> - list_for_each_entry_rcu(intf, &ipmi_interfaces, link) {
> + list_for_each_entry_rcu(intf, &ipmi_interfaces, link,
> + srcu_read_lock_held(&ipmi_interfaces_srcu)) {
> int intf_num = READ_ONCE(intf->intf_num);
>
> if (intf_num == -1)
> @@ -1188,7 +1189,8 @@ 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_rcu(intf, &ipmi_interfaces, link,
> + srcu_read_lock_held(&ipmi_interfaces_srcu)) {
> if (intf->intf_num == if_num)
> goto found;
> }
> @@ -1241,7 +1243,8 @@ int ipmi_get_smi_info(int if_num, struct ipmi_smi_info *data)
> struct ipmi_smi *intf;
>
> index = srcu_read_lock(&ipmi_interfaces_srcu);
> - list_for_each_entry_rcu(intf, &ipmi_interfaces, link) {
> + list_for_each_entry_rcu(intf, &ipmi_interfaces, link,
> + srcu_read_lock_held(&ipmi_interfaces_srcu)) {
> if (intf->intf_num == if_num)
> goto found;
> }
> @@ -4098,7 +4101,8 @@ static int handle_read_event_rsp(struct ipmi_smi *intf,
> * getting events.
> */
> index = srcu_read_lock(&intf->users_srcu);
> - list_for_each_entry_rcu(user, &intf->users, link) {
> + list_for_each_entry_rcu(user, &intf->users, link,
> + srcu_read_lock_held(&intf->users_srcu)) {
> if (!user->gets_events)
> continue;
>
> @@ -4453,7 +4457,8 @@ static void handle_new_recv_msgs(struct ipmi_smi *intf)
> int index;
>
> index = srcu_read_lock(&intf->users_srcu);
> - list_for_each_entry_rcu(user, &intf->users, link) {
> + list_for_each_entry_rcu(user, &intf->users, link,
> + srcu_read_lock_held(&intf->users_srcu)) {
> if (user->handler->ipmi_watchdog_pretimeout)
> user->handler->ipmi_watchdog_pretimeout(
> user->handler_data);
> @@ -4746,7 +4751,8 @@ static void ipmi_timeout(struct timer_list *unused)
> return;
>
> index = srcu_read_lock(&ipmi_interfaces_srcu);
> - list_for_each_entry_rcu(intf, &ipmi_interfaces, link) {
> + list_for_each_entry_rcu(intf, &ipmi_interfaces, link,
> + srcu_read_lock_held(&ipmi_interfaces_srcu)) {
> if (atomic_read(&intf->event_waiters)) {
> intf->ticks_to_req_ev--;
> if (intf->ticks_to_req_ev == 0) {
>
next prev parent reply other threads:[~2020-02-28 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 8:17 Amol Grover
2020-02-28 11:49 ` John Garry [this message]
2020-02-28 17:44 ` 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=b843fa9d-7fd3-940f-fb18-5ce3bef3a9be@huawei.com \
--to=john.garry@huawei.com \
--cc=arnd@arndb.de \
--cc=frextrite@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madhuparnabhowmik10@gmail.com \
--cc=minyard@acm.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 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®