From: "yanjun.zhu" <yanjun.zhu@linux.dev>
To: Leon Romanovsky <leon@kernel.org>
Cc: zyjzyj2000@gmail.com, jgg@ziepe.ca, linux-rdma@vger.kernel.org
Subject: Re: [PATCH 1/1] RDMA/rxe: Fix unsafe socket release during namespace cleanup
Date: Mon, 27 Apr 2026 13:52:17 -0700 [thread overview]
Message-ID: <805dcebc-39c6-4140-b07f-f76b7594c9d8@linux.dev> (raw)
In-Reply-To: <20260427123503.GI440345@unreal>
On 4/27/26 5:35 AM, Leon Romanovsky wrote:
> On Fri, Apr 24, 2026 at 06:35:22AM +0200, Zhu Yanjun wrote:
>> Since all the sockets are created in rdma link create command
>> and destroyed in rdma link delete command, keeping
>> udp_tunnel_sock_release in rxe_ns_exit risks a "double-free" if
>> the namespace and the device are being cleaned up simultaneously.
>
> Please add a ladder diagram to clarify how it can be possible.
Hi, Leon
The double-free occurs as follows:
CPU 0 (Net NameSpace cleanup) CPU 1 (RDMA device removal)
--------------------- ---------------------------
rxe_ns_exit() rxe_link_delete() (rdma link del )
-> sk = ns_sk->rxe_sk4 -> sk = ns_sk->rxe_sk4
-> udp_tunnel_sock_release(sk)
[Success: First Free] -> udp_tunnel_sock_release(sk)
[Crash: Double Free]
After removing the socket release logic from rxe_ns_exit(), we ensure
that only the device destruction path (rxe_link_delete) is responsible
for freeing the tunnel sockets, effectively eliminating the double-free
problem.
I am not sure if I should put the above into the commit log.
Thanks a lot.
Zhu Yanjun
>
> Thanks
>
>>
>> Fixes: 13f2a53c2a71 ("RDMA/rxe: Add net namespace support for IPv4/IPv6 sockets")
>> Signed-off-by: Zhu Yanjun <yanjun.zhu@linux.dev>
>> ---
>> drivers/infiniband/sw/rxe/rxe_ns.c | 20 --------------------
>> 1 file changed, 20 deletions(-)
>>
>> diff --git a/drivers/infiniband/sw/rxe/rxe_ns.c b/drivers/infiniband/sw/rxe/rxe_ns.c
>> index 8b9d734229b2..53add78b8e3a 100644
>> --- a/drivers/infiniband/sw/rxe/rxe_ns.c
>> +++ b/drivers/infiniband/sw/rxe/rxe_ns.c
>> @@ -39,26 +39,6 @@ static void rxe_ns_exit(struct net *net)
>> {
>> /* called when the network namespace is removed
>> */
>> - struct rxe_ns_sock *ns_sk = net_generic(net, rxe_pernet_id);
>> - struct sock *sk;
>> -
>> - rcu_read_lock();
>> - sk = rcu_dereference(ns_sk->rxe_sk4);
>> - rcu_read_unlock();
>> - if (sk) {
>> - rcu_assign_pointer(ns_sk->rxe_sk4, NULL);
>> - udp_tunnel_sock_release(sk->sk_socket);
>> - }
>> -
>> -#if IS_ENABLED(CONFIG_IPV6)
>> - rcu_read_lock();
>> - sk = rcu_dereference(ns_sk->rxe_sk6);
>> - rcu_read_unlock();
>> - if (sk) {
>> - rcu_assign_pointer(ns_sk->rxe_sk6, NULL);
>> - udp_tunnel_sock_release(sk->sk_socket);
>> - }
>> -#endif
>> }
>>
>> /*
>> --
>> 2.43.0
>>
>>
next prev parent reply other threads:[~2026-04-27 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 4:35 [PATCH 1/1] RDMA/rxe: Fix unsafe socket release during namespace cleanup Zhu Yanjun
2026-04-27 12:35 ` Leon Romanovsky
2026-04-27 20:52 ` yanjun.zhu [this message]
2026-04-28 14:26 ` Leon Romanovsky
2026-04-29 13:49 ` Zhu Yanjun
2026-04-29 23:31 ` yanjun.zhu
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=805dcebc-39c6-4140-b07f-f76b7594c9d8@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=zyjzyj2000@gmail.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