mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Linkui Xiao <xiaolinkui@126.com>
Cc: dsahern@kernel.org, idosch@nvidia.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, xiaolinkui@kylinos.cn
Subject: Re: [PATCH net] ipmr, ip6mr: annotate data-races in vif_seq_show()
Date: Tue, 15 Sep 2026 01:10:10 +0000	[thread overview]
Message-ID: <178943461031.1296630.14538685526248597246.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260910093452.2070079-1-xiaolinkui@126.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 10 Sep 2026 17:34:52 +0800 you wrote:
> From: Linkui Xiao <xiaolinkui@kylinos.cn>
> 
> ipmr_vif_seq_show() and ip6mr_vif_seq_show() read vif->bytes_in,
> vif->pkt_in, vif->bytes_out and vif->pkt_out with only rcu_read_lock()
> held: since commit b96ef16d2f83 ("ipmr: convert /proc handlers to
> rcu_read_lock()") both seq_start helpers are annotated __acquires(RCU)
> and no longer take mrt_lock.
> 
> [...]

Here is the summary with links:
  - [net] ipmr, ip6mr: annotate data-races in vif_seq_show()
    https://git.kernel.org/netdev/net-next/c/0019aa65bbc6

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



      reply	other threads:[~2026-09-15  1:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10  9:34 Linkui Xiao
2026-09-15  1:10 ` 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=178943461031.1296630.14538685526248597246.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=xiaolinkui@126.com \
    --cc=xiaolinkui@kylinos.cn \
    /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®