linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: madhuparnabhowmik10@gmail.com
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	kuba@kernel.org, linux-bluetooth@vger.kernel.org,
	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: bluetooth: hci_core: Fix Suspicious RCU usage warnings
Date: Fri, 28 Feb 2020 08:37:03 +0100	[thread overview]
Message-ID: <182A4E2D-86AB-4C81-8ACB-AC8033BAFDE3@holtmann.org> (raw)
In-Reply-To: <20200225130809.32750-1-madhuparnabhowmik10@gmail.com>

Hi Madhuparna,

> The following functions in hci_core are always called with
> hdev->lock held. No need to use list_for_each_entry_rcu(), therefore
> change the usage of list_for_each_entry_rcu() in these functions
> to list_for_each_entry().
> 
> hci_link_keys_clear()
> hci_smp_ltks_clear()
> hci_smp_irks_clear()
> hci_blocked_keys_clear()
> 
> Warning encountered with CONFIG_PROVE_RCU_LIST:
> 
> [   72.213184] =============================
> [   72.213188] WARNING: suspicious RCU usage
> [   72.213192] 5.6.0-rc1+ #5 Not tainted
> [   72.213195] -----------------------------
> [   72.213198] net/bluetooth/hci_core.c:2288 RCU-list traversed in non-reader section!!
> 
> [   72.213676] =============================
> [   72.213679] WARNING: suspicious RCU usage
> [   72.213683] 5.6.0-rc1+ #5 Not tainted
> [   72.213685] -----------------------------
> [   72.213689] net/bluetooth/hci_core.c:2298 RCU-list traversed in non-reader section!!
> 
> [   72.214195] =============================
> [   72.214198] WARNING: suspicious RCU usage
> [   72.214201] 5.6.0-rc1+ #5 Not tainted
> [   72.214204] -----------------------------
> [   72.214208] net/bluetooth/hci_core.c:2308 RCU-list traversed in non-reader section!!
> 
> [  333.456972] =============================
> [  333.456979] WARNING: suspicious RCU usage
> [  333.457001] 5.6.0-rc1+ #5 Not tainted
> [  333.457007] -----------------------------
> [  333.457014] net/bluetooth/hci_core.c:2318 RCU-list traversed in non-reader section!!
> 
> Signed-off-by: Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>
> ---
> net/bluetooth/hci_core.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)

patch has been applied to bluetooth-next tree.

Regards

Marcel


      reply	other threads:[~2020-02-28  7:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-25 13:08 [PATCH] net: bluetooth: hci_core: Fix Suspicious RCU usage warnings madhuparnabhowmik10
2020-02-28  7:37 ` Marcel Holtmann [this message]

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=182A4E2D-86AB-4C81-8ACB-AC8033BAFDE3@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=davem@davemloft.net \
    --cc=frextrite@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=johan.hedberg@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-bluetooth@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).