From: patchwork-bot+netdevbpf@kernel.org
To: Runyu Xiao <runyu.xiao@seu.edu.cn>
Cc: netdev@vger.kernel.org, kuniyu@google.com, edumazet@google.com,
davem@davemloft.net, dsahern@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org,
linux-kernel@vger.kernel.org, jianhao.xu@seu.edu.cn
Subject: Re: [PATCH net v4] raw: annotate lockless match fields in raw_v4_match()
Date: Thu, 23 Jul 2026 15:20:18 +0000 [thread overview]
Message-ID: <178482001813.2315735.14825927789469935052.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260716142958.3064224-1-runyu.xiao@seu.edu.cn>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 16 Jul 2026 22:29:58 +0800 you wrote:
> raw_v4_match() is a lockless match helper under sk_for_each_rcu(). It
> still reads inet->inet_daddr, inet->inet_rcv_saddr and
> sk->sk_bound_dev_if with plain loads while bind, connect and
> bind-to-device paths can update the same match fields concurrently.
>
> Annotate only those mutable match fields in raw_v4_match(), and do so
> at the point of use instead of hoisting the bound-device read before
> the earlier short-circuit tests.
>
> [...]
Here is the summary with links:
- [net,v4] raw: annotate lockless match fields in raw_v4_match()
https://git.kernel.org/netdev/net/c/18f116931f52
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-07-23 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 14:29 [PATCH net v4] raw: annotate lockless match fields in raw_v4_match() Runyu Xiao
2026-07-23 15:20 ` 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=178482001813.2315735.14825927789469935052.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=jianhao.xu@seu.edu.cn \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=runyu.xiao@seu.edu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.