From: joel@joelfernandes.org
To: "Rafael J. Wysocki" <rafael@kernel.org>, madhuparnabhowmik10@gmail.com
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Pavel Machek <pavel@ucw.cz>, Len Brown <len.brown@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
frextrite@gmail.com,
linux-kernel-mentees@lists.linuxfoundation.org,
paulmck@kernel.org
Subject: Re: [PATCH 1/2] drivers: base: power: main: Use built-in RCU list checking
Date: Sun, 01 Mar 2020 15:53:07 -0500 [thread overview]
Message-ID: <C2E57D31-A459-4F5F-8ECF-484FBB26C065@joelfernandes.org> (raw)
In-Reply-To: <CAJZ5v0jhw+cVm=ViiOtZgKr+a1L_PbeVPNXpsPbgghUvMPODSA@mail.gmail.com>
On March 1, 2020 3:12:53 PM EST, "Rafael J. Wysocki" <rafael@kernel.org> wrote:
>On Fri, Feb 28, 2020 at 6:47 PM <madhuparnabhowmik10@gmail.com> wrote:
>>
>> From: Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>
>>
>> This patch passes the cond argument to list_for_each_entry_rcu()
>> to fix the following false-positive lockdep warnings:
>>
>> [ 330.302784] =============================
>> [ 330.302789] WARNING: suspicious RCU usage
>> [ 330.302796] 5.6.0-rc1+ #5 Not tainted
>> [ 330.302801] -----------------------------
>> [ 330.302808] drivers/base/power/main.c:326 RCU-list traversed in
>non-reader section!!
>>
>> [ 330.303303] =============================
>> [ 330.303307] WARNING: suspicious RCU usage
>> [ 330.303311] 5.6.0-rc1+ #5 Not tainted
>> [ 330.303315] -----------------------------
>> [ 330.303319] drivers/base/power/main.c:1698 RCU-list traversed in
>non-reader section!!
>>
>> [ 331.934969] =============================
>> [ 331.934971] WARNING: suspicious RCU usage
>> [ 331.934973] 5.6.0-rc1+ #5 Not tainted
>> [ 331.934975] -----------------------------
>> [ 331.934977] drivers/base/power/main.c:1238 RCU-list traversed in
>non-reader section!!
>>
>> [ 332.467772] WARNING: suspicious RCU usage
>> [ 332.467775] 5.6.0-rc1+ #5 Not tainted
>> [ 332.467775] -----------------------------
>> [ 332.467778] drivers/base/power/main.c:269 RCU-list traversed in
>non-reader section!!
>
>I don't see these warnings in the kernels run locally here.
>
>What do you do to get them?
>
>Joel, any comments here?
You have to enable lockdep in your config. Does your setup have that?
Thanks,
- Joel
>
>>
>> Signed-off-by: Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>
>> ---
>> drivers/base/power/main.c | 12 ++++++++----
>> 1 file changed, 8 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/base/power/main.c b/drivers/base/power/main.c
>> index 0e99a760aebd..742c05f3c1e7 100644
>> --- a/drivers/base/power/main.c
>> +++ b/drivers/base/power/main.c
>> @@ -266,7 +266,8 @@ static void dpm_wait_for_suppliers(struct device
>*dev, bool async)
>> * callbacks freeing the link objects for the links in the
>list we're
>> * walking.
>> */
>> - list_for_each_entry_rcu(link, &dev->links.suppliers, c_node)
>> + list_for_each_entry_rcu(link, &dev->links.suppliers, c_node,
>> + device_links_read_lock_held())
>> if (READ_ONCE(link->status) != DL_STATE_DORMANT)
>> dpm_wait(link->supplier, async);
>>
>> @@ -323,7 +324,8 @@ static void dpm_wait_for_consumers(struct device
>*dev, bool async)
>> * continue instead of trying to continue in parallel with
>its
>> * unregistration).
>> */
>> - list_for_each_entry_rcu(link, &dev->links.consumers, s_node)
>> + list_for_each_entry_rcu(link, &dev->links.consumers, s_node,
>> + device_links_read_lock_held())
>> if (READ_ONCE(link->status) != DL_STATE_DORMANT)
>> dpm_wait(link->consumer, async);
>>
>> @@ -1235,7 +1237,8 @@ static void dpm_superior_set_must_resume(struct
>device *dev)
>>
>> idx = device_links_read_lock();
>>
>> - list_for_each_entry_rcu(link, &dev->links.suppliers, c_node)
>> + list_for_each_entry_rcu(link, &dev->links.suppliers, c_node,
>> + device_links_read_lock_held())
>> link->supplier->power.must_resume = true;
>>
>> device_links_read_unlock(idx);
>> @@ -1695,7 +1698,8 @@ static void
>dpm_clear_superiors_direct_complete(struct device *dev)
>>
>> idx = device_links_read_lock();
>>
>> - list_for_each_entry_rcu(link, &dev->links.suppliers, c_node)
>{
>> + list_for_each_entry_rcu(link, &dev->links.suppliers, c_node,
>> + device_links_read_lock_held()) {
>> spin_lock_irq(&link->supplier->power.lock);
>> link->supplier->power.direct_complete = false;
>> spin_unlock_irq(&link->supplier->power.lock);
>> --
>> 2.17.1
>>
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2020-03-01 20:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 17:46 madhuparnabhowmik10
2020-03-01 20:12 ` Rafael J. Wysocki
2020-03-01 20:53 ` joel [this message]
2020-03-01 21:23 ` Rafael J. Wysocki
2020-03-01 22:18 ` Joel Fernandes
[not found] ` <CAD=jOEZ3vdNC4qTMxptaXLjs7i8TCTYjeiv9vXhcapLSkrr9RQ@mail.gmail.com>
2020-03-02 17:02 ` Rafael J. Wysocki
2020-03-03 16:09 ` Madhuparna Bhowmik
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=C2E57D31-A459-4F5F-8ECF-484FBB26C065@joelfernandes.org \
--to=joel@joelfernandes.org \
--cc=frextrite@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=madhuparnabhowmik10@gmail.com \
--cc=paulmck@kernel.org \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/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®