From: Jiri Pirko <jiri@resnulli.us>
To: madhuparnabhowmik10@gmail.com
Cc: paulmck@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, jiri@mellanox.com,
joel@joelfernandes.org,
linux-kernel-mentees@lists.linuxfoundation.org,
davem@davemloft.net
Subject: Re: [Linux-kernel-mentees] [PATCH] net: core: devlink.c: Use built-in RCU list checking
Date: Tue, 25 Feb 2020 14:06:46 +0100 [thread overview]
Message-ID: <20200225130646.GD17869@nanopsycho> (raw)
In-Reply-To: <20200225122745.31095-1-madhuparnabhowmik10@gmail.com>
Tue, Feb 25, 2020 at 01:27:45PM CET, madhuparnabhowmik10@gmail.com wrote:
>From: Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>
>
>list_for_each_entry_rcu() has built-in RCU and lock checking.
>
>Pass cond argument to list_for_each_entry_rcu() to silence
>false lockdep warning when CONFIG_PROVE_RCU_LIST is enabled.
>
>The devlink->lock is held when devlink_dpipe_table_find()
>is called in non RCU read side section. Therefore, pass struct devlink
>to devlink_dpipe_table_find() for lockdep checking.
>
>Signed-off-by: Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>
Reviewed-by: Jiri Pirko <jiri@mellanox.com>
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
WARNING: multiple messages have this Message-ID (diff)
From: Jiri Pirko <jiri@resnulli.us>
To: madhuparnabhowmik10@gmail.com
Cc: jiri@mellanox.com, davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, joel@joelfernandes.org,
linux-kernel-mentees@lists.linuxfoundation.org,
frextrite@gmail.com, paulmck@kernel.org
Subject: Re: [PATCH] net: core: devlink.c: Use built-in RCU list checking
Date: Tue, 25 Feb 2020 14:06:46 +0100 [thread overview]
Message-ID: <20200225130646.GD17869@nanopsycho> (raw)
In-Reply-To: <20200225122745.31095-1-madhuparnabhowmik10@gmail.com>
Tue, Feb 25, 2020 at 01:27:45PM CET, madhuparnabhowmik10@gmail.com wrote:
>From: Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>
>
>list_for_each_entry_rcu() has built-in RCU and lock checking.
>
>Pass cond argument to list_for_each_entry_rcu() to silence
>false lockdep warning when CONFIG_PROVE_RCU_LIST is enabled.
>
>The devlink->lock is held when devlink_dpipe_table_find()
>is called in non RCU read side section. Therefore, pass struct devlink
>to devlink_dpipe_table_find() for lockdep checking.
>
>Signed-off-by: Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>
Reviewed-by: Jiri Pirko <jiri@mellanox.com>
next prev parent reply other threads:[~2020-02-25 13:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 12:27 [Linux-kernel-mentees] [PATCH] net: core: devlink.c: Use built-in RCU list checking madhuparnabhowmik10
2020-02-25 12:27 ` madhuparnabhowmik10
2020-02-25 13:06 ` Jiri Pirko [this message]
2020-02-25 13:06 ` Jiri Pirko
2020-02-27 0:59 ` [Linux-kernel-mentees] " David Miller
2020-02-27 0:59 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2020-02-24 9:30 [Linux-kernel-mentees] " madhuparnabhowmik10
2020-02-24 10:52 ` Jiri Pirko
2020-02-25 12:09 ` Madhuparna Bhowmik
2020-02-21 16:51 madhuparnabhowmik10
2020-02-21 17:20 ` Jiri Pirko
2020-02-21 17:35 ` Madhuparna Bhowmik
2020-02-21 17:54 ` Jiri Pirko
2020-02-21 18:00 ` Madhuparna Bhowmik
2020-02-23 11:03 ` Madhuparna Bhowmik
2020-02-23 18:19 ` Jiri Pirko
2020-02-24 0:28 ` kbuild test robot
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=20200225130646.GD17869@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=jiri@mellanox.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madhuparnabhowmik10@gmail.com \
--cc=netdev@vger.kernel.org \
--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.