netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	danishanwar@ti.com, aleksander.lobakin@intel.com,
	jkarrenpalo@gmail.com, ffmancera@riseup.net, m-karicheri2@ti.com,
	w-kwok2@ti.com, sdf@fomichev.me, shaw.leon@gmail.com,
	kuniyu@google.com, johannes.berg@intel.com
Subject: Re: [PATCHv3 net 0/3] hsr: fix lock warnings
Date: Thu, 11 Sep 2025 10:00:10 +0000	[thread overview]
Message-ID: <175758481000.2111220.9133355374443467875.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250905091533.377443-1-liuhangbin@gmail.com>

Hello:

This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Fri,  5 Sep 2025 09:15:30 +0000 you wrote:
> hsr_for_each_port is called in many places without holding the RCU read
> lock, this may trigger warnings on debug kernels like:
> 
>   [   40.457015] [  T201] WARNING: suspicious RCU usage
>   [   40.457020] [  T201] 6.17.0-rc2-virtme #1 Not tainted
>   [   40.457025] [  T201] -----------------------------
>   [   40.457029] [  T201] net/hsr/hsr_main.c:137 RCU-list traversed in non-reader section!!
>   [   40.457036] [  T201]
>                           other info that might help us debug this:
> 
> [...]

Here is the summary with links:
  - [PATCHv3,net,1/3] hsr: use rtnl lock when iterating over ports
    https://git.kernel.org/netdev/net/c/8884c6939913
  - [PATCHv3,net,2/3] hsr: use hsr_for_each_port_rtnl in hsr_port_get_hsr
    https://git.kernel.org/netdev/net/c/393c841fe433
  - [PATCHv3,net,3/3] hsr: hold rcu and dev lock for hsr_get_port_ndev
    https://git.kernel.org/netdev/net/c/847748fc66d0

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



      parent reply	other threads:[~2025-09-11 10:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-05  9:15 [PATCHv3 net 0/3] hsr: fix lock warnings Hangbin Liu
2025-09-05  9:15 ` [PATCHv3 net 1/3] hsr: use rtnl lock when iterating over ports Hangbin Liu
2025-09-10 17:06   ` Simon Horman
2025-09-05  9:15 ` [PATCHv3 net 2/3] hsr: use hsr_for_each_port_rtnl in hsr_port_get_hsr Hangbin Liu
2025-09-10 17:07   ` Simon Horman
2025-09-05  9:15 ` [PATCHv3 net 3/3] hsr: hold rcu and dev lock for hsr_get_port_ndev Hangbin Liu
2025-09-10 17:09   ` Simon Horman
2025-09-11 10:00 ` 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=175758481000.2111220.9133355374443467875.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=aleksander.lobakin@intel.com \
    --cc=danishanwar@ti.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=ffmancera@riseup.net \
    --cc=horms@kernel.org \
    --cc=jkarrenpalo@gmail.com \
    --cc=johannes.berg@intel.com \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=liuhangbin@gmail.com \
    --cc=m-karicheri2@ti.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    --cc=shaw.leon@gmail.com \
    --cc=w-kwok2@ti.com \
    /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).