public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jeremy Kerr <jk@codeconstruct.com.au>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
	linux-kernel@vger.kernel.org, lkp@lists.01.org, lkp@intel.com,
	kuba@kernel.org, matt@codeconstruct.com.au
Subject: Re: [PATCH net] mctp: perform route destruction under RCU read lock
Date: Wed, 08 Sep 2021 10:40:08 +0000	[thread overview]
Message-ID: <163109760826.16056.8641773139555261021.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210908041310.4014458-1-jk@codeconstruct.com.au>

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Wed,  8 Sep 2021 12:13:10 +0800 you wrote:
> The kernel test robot reports:
> 
>   [  843.509974][  T345] =============================
>   [  843.524220][  T345] WARNING: suspicious RCU usage
>   [  843.538791][  T345] 5.14.0-rc2-00606-g889b7da23abf #1 Not tainted
>   [  843.553617][  T345] -----------------------------
>   [  843.567412][  T345] net/mctp/route.c:310 RCU-list traversed in non-reader section!!
> 
> [...]

Here is the summary with links:
  - [net] mctp: perform route destruction under RCU read lock
    https://git.kernel.org/netdev/net/c/581edcd0c8a0

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2021-09-08 10:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-08  3:03 [mctp] 889b7da23a: net/mctp/route.c:#RCU-list_traversed_in_non-reader_section kernel test robot
2021-09-08  4:13 ` [PATCH net] mctp: perform route destruction under RCU read lock Jeremy Kerr
2021-09-08 10:40   ` patchwork-bot+netdevbpf [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=163109760826.16056.8641773139555261021.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=jk@codeconstruct.com.au \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=matt@codeconstruct.com.au \
    --cc=netdev@vger.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