linux-kernel - Re: [PATCH net-next v5 2/6] vxlan: drop sock

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aFJ3tnfby14zIBm8@shredder>
Date: Wed, 18 Jun 2025 11:24:22 +0300
From: Ido Schimmel <idosch@...dia.com>
To: Stanislav Fomichev <stfomichev@...il.com>
Cc: netdev@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com,
	kuba@...nel.org, pabeni@...hat.com, skalluru@...vell.com,
	manishc@...vell.com, andrew+netdev@...n.ch,
	michael.chan@...adcom.com, pavan.chebbi@...adcom.com,
	ajit.khaparde@...adcom.com, sriharsha.basavapatna@...adcom.com,
	somnath.kotur@...adcom.com, anthony.l.nguyen@...el.com,
	przemyslaw.kitszel@...el.com, tariqt@...dia.com, saeedm@...dia.com,
	louis.peens@...igine.com, shshaikh@...vell.com,
	GR-Linux-NIC-Dev@...vell.com, ecree.xilinx@...il.com,
	horms@...nel.org, dsahern@...nel.org, shuah@...nel.org,
	tglx@...utronix.de, mingo@...nel.org, ruanjinjie@...wei.com,
	razor@...ckwall.org, petrm@...dia.com, kuniyu@...gle.com,
	sdf@...ichev.me, linux-kernel@...r.kernel.org,
	intel-wired-lan@...ts.osuosl.org, linux-rdma@...r.kernel.org,
	oss-drivers@...igine.com, linux-net-drivers@....com,
	linux-kselftest@...r.kernel.org, leon@...nel.org
Subject: Re: [PATCH net-next v5 2/6] vxlan: drop sock_lock

On Mon, Jun 16, 2025 at 09:21:13AM -0700, Stanislav Fomichev wrote:
> We won't be able to sleep soon in vxlan_offload_rx_ports and won't be
> able to grab sock_lock. Instead of having separate spinlock to
> manage sockets, rely on rtnl lock. This is similar to how geneve
> manages its sockets.
> 
> Signed-off-by: Stanislav Fomichev <stfomichev@...il.com>

Reviewed-by: Ido Schimmel <idosch@...dia.com>