From: Nikolay Aleksandrov <razor@blackwall.org>
To: Stanislav Fomichev <stfomichev@gmail.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, skalluru@marvell.com, manishc@marvell.com,
andrew+netdev@lunn.ch, michael.chan@broadcom.com,
pavan.chebbi@broadcom.com, ajit.khaparde@broadcom.com,
sriharsha.basavapatna@broadcom.com, somnath.kotur@broadcom.com,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
tariqt@nvidia.com, saeedm@nvidia.com, louis.peens@corigine.com,
shshaikh@marvell.com, GR-Linux-NIC-Dev@marvell.com,
ecree.xilinx@gmail.com, horms@kernel.org, dsahern@kernel.org,
shuah@kernel.org, tglx@linutronix.de, mingo@kernel.org,
ruanjinjie@huawei.com, idosch@nvidia.com, petrm@nvidia.com,
kuniyu@google.com, sdf@fomichev.me, linux-kernel@vger.kernel.org,
intel-wired-lan@lists.osuosl.org, linux-rdma@vger.kernel.org,
oss-drivers@corigine.com, linux-net-drivers@amd.com,
linux-kselftest@vger.kernel.org, leon@kernel.org
Subject: Re: [PATCH net-next v5 1/6] geneve: rely on rtnl lock in geneve_offload_rx_ports
Date: Wed, 18 Jun 2025 18:14:06 +0300 [thread overview]
Message-ID: <22ec7ed6-9c38-4f81-9ec4-024da12b8710@blackwall.org> (raw)
In-Reply-To: <20250616162117.287806-2-stfomichev@gmail.com>
On 6/16/25 19:21, Stanislav Fomichev wrote:
> udp_tunnel_push_rx_port will grab mutex in the next patch so
> we can't use rcu. geneve_offload_rx_ports is called
> from geneve_netdevice_event for NETDEV_UDP_TUNNEL_PUSH_INFO and
> NETDEV_UDP_TUNNEL_DROP_INFO which both have ASSERT_RTNL.
> Entries are added to and removed from the sock_list under rtnl
> lock as well (when adding or removing a tunneling device).
>
> Signed-off-by: Stanislav Fomichev <stfomichev@gmail.com>
> ---
> drivers/net/geneve.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/geneve.c b/drivers/net/geneve.c
> index ffc15a432689..9efedc6758bf 100644
> --- a/drivers/net/geneve.c
> +++ b/drivers/net/geneve.c
> @@ -41,6 +41,7 @@ MODULE_PARM_DESC(log_ecn_error, "Log packets received with corrupted ECN");
> /* per-network namespace private data for this module */
> struct geneve_net {
> struct list_head geneve_list;
> + /* sock_list is protected by rtnl lock */
> struct list_head sock_list;
> };
>
> @@ -1179,8 +1180,9 @@ static void geneve_offload_rx_ports(struct net_device *dev, bool push)
> struct geneve_net *gn = net_generic(net, geneve_net_id);
> struct geneve_sock *gs;
>
> - rcu_read_lock();
> - list_for_each_entry_rcu(gs, &gn->sock_list, list) {
> + ASSERT_RTNL();
> +
> + list_for_each_entry(gs, &gn->sock_list, list) {
> if (push) {
> udp_tunnel_push_rx_port(dev, gs->sock,
> UDP_TUNNEL_TYPE_GENEVE);
> @@ -1189,7 +1191,6 @@ static void geneve_offload_rx_ports(struct net_device *dev, bool push)
> UDP_TUNNEL_TYPE_GENEVE);
> }
> }
> - rcu_read_unlock();
> }
>
> /* Initialize the device structure. */
Reviewed-by: Nikolay Aleksandrov <razor@blackwall.org>
next prev parent reply other threads:[~2025-06-18 15:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 16:21 [PATCH net-next v5 0/6] udp_tunnel: remove rtnl_lock dependency Stanislav Fomichev
2025-06-16 16:21 ` [PATCH net-next v5 1/6] geneve: rely on rtnl lock in geneve_offload_rx_ports Stanislav Fomichev
2025-06-18 15:14 ` Nikolay Aleksandrov [this message]
2025-06-16 16:21 ` [PATCH net-next v5 2/6] vxlan: drop sock_lock Stanislav Fomichev
2025-06-18 8:24 ` Ido Schimmel
2025-06-18 15:13 ` Nikolay Aleksandrov
2025-06-16 16:21 ` [PATCH net-next v5 3/6] udp_tunnel: remove rtnl_lock dependency Stanislav Fomichev
2025-06-16 16:21 ` [PATCH net-next v5 4/6] net: remove redundant ASSERT_RTNL() in queue setup functions Stanislav Fomichev
2025-06-16 16:21 ` [PATCH net-next v5 5/6] netdevsim: remove udp_ports_sleep Stanislav Fomichev
2025-06-16 16:21 ` [PATCH net-next v5 6/6] Revert "bnxt_en: bring back rtnl_lock() in the bnxt_open() path" Stanislav Fomichev
2025-06-19 2:00 ` [PATCH net-next v5 0/6] udp_tunnel: remove rtnl_lock dependency patchwork-bot+netdevbpf
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=22ec7ed6-9c38-4f81-9ec4-024da12b8710@blackwall.org \
--to=razor@blackwall.org \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=linux-rdma@vger.kernel.org \
--cc=louis.peens@corigine.com \
--cc=manishc@marvell.com \
--cc=michael.chan@broadcom.com \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=petrm@nvidia.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=ruanjinjie@huawei.com \
--cc=saeedm@nvidia.com \
--cc=sdf@fomichev.me \
--cc=shshaikh@marvell.com \
--cc=shuah@kernel.org \
--cc=skalluru@marvell.com \
--cc=somnath.kotur@broadcom.com \
--cc=sriharsha.basavapatna@broadcom.com \
--cc=stfomichev@gmail.com \
--cc=tariqt@nvidia.com \
--cc=tglx@linutronix.de \
/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).