From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, kuniyu@amazon.com, horms@kernel.org,
eric.dumazet@gmail.com
Subject: Re: [PATCH v4 net 00/12] net: first round to use dev_net_rcu()
Date: Fri, 07 Feb 2025 00:30:35 +0000 [thread overview]
Message-ID: <173888823503.1713650.11309572430849516645.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250205155120.1676781-1-edumazet@google.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 5 Feb 2025 15:51:08 +0000 you wrote:
> dev_net(dev) should either be protected by RTNL or RCU.
>
> There is no LOCKDEP support yet for this helper.
>
> Adding it would trigger too many splats.
>
> Instead, add dev_net_rcu() for rcu_read_lock() contexts
> and start to use it to fix bugs and clearly document the
> safety requirements.
>
> [...]
Here is the summary with links:
- [v4,net,01/12] net: add dev_net_rcu() helper
https://git.kernel.org/netdev/net/c/482ad2a4ace2
- [v4,net,02/12] ipv4: add RCU protection to ip4_dst_hoplimit()
https://git.kernel.org/netdev/net/c/469308552ca4
- [v4,net,03/12] ipv4: use RCU protection in ip_dst_mtu_maybe_forward()
https://git.kernel.org/netdev/net/c/071d8012869b
- [v4,net,04/12] ipv4: use RCU protection in ipv4_default_advmss()
https://git.kernel.org/netdev/net/c/71b8471c93fa
- [v4,net,05/12] ipv4: use RCU protection in rt_is_expired()
https://git.kernel.org/netdev/net/c/dd205fcc33d9
- [v4,net,06/12] ipv4: use RCU protection in inet_select_addr()
https://git.kernel.org/netdev/net/c/719817cd293e
- [v4,net,07/12] ipv4: use RCU protection in __ip_rt_update_pmtu()
https://git.kernel.org/netdev/net/c/139512191bd0
- [v4,net,08/12] ipv4: icmp: convert to dev_net_rcu()
https://git.kernel.org/netdev/net/c/4b8474a0951e
- [v4,net,09/12] flow_dissector: use RCU protection to fetch dev_net()
https://git.kernel.org/netdev/net/c/afec62cd0a41
- [v4,net,10/12] ipv6: use RCU protection in ip6_default_advmss()
https://git.kernel.org/netdev/net/c/3c8ffcd248da
- [v4,net,11/12] ipv6: icmp: convert to dev_net_rcu()
https://git.kernel.org/netdev/net/c/34aef2b0ce3a
- [v4,net,12/12] ipv6: Use RCU in ip6_input()
https://git.kernel.org/netdev/net/c/b768294d449d
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-02-07 0:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 15:51 [PATCH v4 net 00/12] net: first round to use dev_net_rcu() Eric Dumazet
2025-02-05 15:51 ` [PATCH v4 net 01/12] net: add dev_net_rcu() helper Eric Dumazet
2025-02-05 15:51 ` [PATCH v4 net 02/12] ipv4: add RCU protection to ip4_dst_hoplimit() Eric Dumazet
2025-02-05 15:51 ` [PATCH v4 net 03/12] ipv4: use RCU protection in ip_dst_mtu_maybe_forward() Eric Dumazet
2025-02-05 15:51 ` [PATCH v4 net 04/12] ipv4: use RCU protection in ipv4_default_advmss() Eric Dumazet
2025-02-05 15:51 ` [PATCH v4 net 05/12] ipv4: use RCU protection in rt_is_expired() Eric Dumazet
2025-02-05 15:51 ` [PATCH v4 net 06/12] ipv4: use RCU protection in inet_select_addr() Eric Dumazet
2025-02-05 15:51 ` [PATCH v4 net 07/12] ipv4: use RCU protection in __ip_rt_update_pmtu() Eric Dumazet
2025-02-05 15:51 ` [PATCH v4 net 08/12] ipv4: icmp: convert to dev_net_rcu() Eric Dumazet
2025-02-05 15:51 ` [PATCH v4 net 09/12] flow_dissector: use RCU protection to fetch dev_net() Eric Dumazet
2025-02-05 15:51 ` [PATCH v4 net 10/12] ipv6: use RCU protection in ip6_default_advmss() Eric Dumazet
2025-02-05 15:51 ` [PATCH v4 net 11/12] ipv6: icmp: convert to dev_net_rcu() Eric Dumazet
2025-02-05 15:51 ` [PATCH v4 net 12/12] ipv6: Use RCU in ip6_input() Eric Dumazet
2025-02-07 0:30 ` 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=173888823503.1713650.11309572430849516645.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.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).