From: patchwork-bot+netdevbpf@kernel.org
To: luoxuanqiang <xuanqiang.luo@linux.dev>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, dsahern@kernel.org, idosch@nvidia.com,
horms@kernel.org, kuniyu@google.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/2] ipv4: update rt_flush_dev() and two dst.dev readers
Date: Tue, 21 Jul 2026 10:00:13 +0000 [thread overview]
Message-ID: <178462801320.197248.14976916852856571721.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260708060537.17188-1-xuanqiang.luo@linux.dev>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 8 Jul 2026 14:05:35 +0800 you wrote:
> From: Xuanqiang Luo <xuanqiang.luo@linux.dev>
>
> Patch 1 makes the rt_flush_dev() write to rt->dst.dev use
> rcu_assign_pointer(), matching the existing dst_dev_rcu() readers.
>
> Patch 2 makes ip_rt_send_redirect() and ip_rt_get_source() use one
> dst.dev snapshot throughout each operation, so a concurrent rt_flush_dev()
> update cannot make them use values from two devices.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] ipv4: use rcu_assign_pointer() in rt_flush_dev()
https://git.kernel.org/netdev/net-next/c/1469773b246a
- [net-next,v3,2/2] ipv4: snapshot dst.dev in ip_rt_send_redirect() and ip_rt_get_source()
https://git.kernel.org/netdev/net-next/c/7804eaa057fe
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-21 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 6:05 [PATCH net-next v3 0/2] ipv4: update rt_flush_dev() and two dst.dev readers xuanqiang.luo
2026-07-08 6:05 ` [PATCH net-next v3 1/2] ipv4: use rcu_assign_pointer() in rt_flush_dev() xuanqiang.luo
2026-07-13 15:58 ` Ido Schimmel
2026-07-08 6:05 ` [PATCH net-next v3 2/2] ipv4: snapshot dst.dev in ip_rt_send_redirect() and ip_rt_get_source() xuanqiang.luo
2026-07-13 15:59 ` Ido Schimmel
2026-07-21 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=178462801320.197248.14976916852856571721.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=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=xuanqiang.luo@linux.dev \
/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