From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
ncardwell@google.com, horms@kernel.org, kuniyu@google.com,
dsahern@kernel.org, netdev@vger.kernel.org,
eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 0/8] net: add rcu safety to dst->dev
Date: Sat, 30 Aug 2025 02:50:22 +0000 [thread overview]
Message-ID: <175652222248.2402606.1552365680516808739.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250828195823.3958522-1-edumazet@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 28 Aug 2025 19:58:15 +0000 you wrote:
> Followup of commit 88fe14253e18 ("net: dst: add four helpers
> to annotate data-races around dst->dev").
>
> Use lockdep enabled helpers to convert our unsafe dst->dev
> uses one at a time.
>
> More to come...
>
> [...]
Here is the summary with links:
- [net-next,1/8] net: dst: introduce dst->dev_rcu
https://git.kernel.org/netdev/net-next/c/caedcc5b6df1
- [net-next,2/8] ipv6: start using dst_dev_rcu()
https://git.kernel.org/netdev/net-next/c/b775ecf1655c
- [net-next,3/8] ipv6: use RCU in ip6_xmit()
https://git.kernel.org/netdev/net-next/c/9085e56501d9
- [net-next,4/8] ipv6: use RCU in ip6_output()
https://git.kernel.org/netdev/net-next/c/11709573cc4e
- [net-next,5/8] net: use dst_dev_rcu() in sk_setup_caps()
https://git.kernel.org/netdev/net-next/c/99a2ace61b21
- [net-next,6/8] tcp_metrics: use dst_dev_net_rcu()
https://git.kernel.org/netdev/net-next/c/50c127a69cd6
- [net-next,7/8] tcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check()
https://git.kernel.org/netdev/net-next/c/b62a59c18b69
- [net-next,8/8] ipv4: start using dst_dev_rcu()
https://git.kernel.org/netdev/net-next/c/6ad8de3cefdb
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:[~2025-08-30 2:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 19:58 [PATCH net-next 0/8] net: add rcu safety to dst->dev Eric Dumazet
2025-08-28 19:58 ` [PATCH net-next 1/8] net: dst: introduce dst->dev_rcu Eric Dumazet
2025-08-28 21:53 ` David Ahern
2025-08-28 19:58 ` [PATCH net-next 2/8] ipv6: start using dst_dev_rcu() Eric Dumazet
2025-08-28 21:46 ` David Ahern
2025-08-28 19:58 ` [PATCH net-next 3/8] ipv6: use RCU in ip6_xmit() Eric Dumazet
2025-08-28 21:53 ` David Ahern
2025-08-28 19:58 ` [PATCH net-next 4/8] ipv6: use RCU in ip6_output() Eric Dumazet
2025-08-28 22:01 ` David Ahern
2025-08-28 19:58 ` [PATCH net-next 5/8] net: use dst_dev_rcu() in sk_setup_caps() Eric Dumazet
2025-08-28 22:12 ` David Ahern
2025-08-28 19:58 ` [PATCH net-next 6/8] tcp_metrics: use dst_dev_net_rcu() Eric Dumazet
2025-08-28 22:14 ` David Ahern
2025-08-28 19:58 ` [PATCH net-next 7/8] tcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check() Eric Dumazet
2025-08-28 22:16 ` David Ahern
2025-08-28 19:58 ` [PATCH net-next 8/8] ipv4: start using dst_dev_rcu() Eric Dumazet
2025-08-28 22:17 ` David Ahern
2025-08-30 2:50 ` 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=175652222248.2402606.1552365680516808739.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).