From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Stefan Metzmacher <metze@samba.org>, linux-rdma@vger.kernel.org
Cc: Zhu Yanjun <zyjzyj2000@gmail.com>, Jason Gunthorpe <jgg@ziepe.ca>,
Leon Romanovsky <leon@kernel.org>,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
netdev@vger.kernel.org, linux-cifs@vger.kernel.org
Subject: Re: [PATCH] RDMA/rxe: let rxe_reclassify_recv_socket() call sk_owner_put()
Date: Fri, 19 Dec 2025 19:51:37 -0800 [thread overview]
Message-ID: <9ccc0635-7c0e-4a18-8469-9c5b6d9b268f@linux.dev> (raw)
In-Reply-To: <20251219140408.2300163-1-metze@samba.org>
在 2025/12/19 6:04, Stefan Metzmacher 写道:
> On kernels build with CONFIG_PROVE_LOCKING, CONFIG_MODULES
> and CONFIG_DEBUG_LOCK_ALLOC 'rmmod rdma_rxe' is no longer
> possible.
>
> For the global recv sockets rxe_net_exit() is where we
> call rxe_release_udp_tunnel-> udp_tunnel_sock_release(),
> which means the sockets are destroyed before 'rmmod rdma_rxe'
> finishes, so there's no need to protect against
> rxe_recv_slock_key and rxe_recv_sk_key disappearing
> while the sockets are still alive.
>
> Fixes: 80a85a771deb ("RDMA/rxe: reclassify sockets in order to avoid false positives from lockdep")
> Cc: Zhu Yanjun <zyjzyj2000@gmail.com>
> Cc: Jason Gunthorpe <jgg@ziepe.ca>
> Cc: Leon Romanovsky <leon@kernel.org>
> Cc: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
> Cc: linux-rdma@vger.kernel.org
> Cc: netdev@vger.kernel.org
> Cc: linux-cifs@vger.kernel.org
> Signed-off-by: Stefan Metzmacher <metze@samba.org>
Thanks a lot. IIRC, there is a similar commit for SIW driver. Thus, I am
not sure if there is a similar problem in SIW driver or not.
Reviewed-by: Zhu Yanjun <yanjun.zhu@linux.dev>
Zhu Yanjun
> ---
> drivers/infiniband/sw/rxe/rxe_net.c | 32 +++++++++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
>
> diff --git a/drivers/infiniband/sw/rxe/rxe_net.c b/drivers/infiniband/sw/rxe/rxe_net.c
> index 0195d361e5e3..0bd0902b11f7 100644
> --- a/drivers/infiniband/sw/rxe/rxe_net.c
> +++ b/drivers/infiniband/sw/rxe/rxe_net.c
> @@ -64,7 +64,39 @@ static inline void rxe_reclassify_recv_socket(struct socket *sock)
> break;
> default:
> WARN_ON_ONCE(1);
> + return;
> }
> + /*
> + * sock_lock_init_class_and_name() calls
> + * sk_owner_set(sk, THIS_MODULE); in order
> + * to make sure the referenced global
> + * variables rxe_recv_slock_key and
> + * rxe_recv_sk_key are not removed
> + * before the socket is closed.
> + *
> + * However this prevents rxe_net_exit()
> + * from being called and 'rmmod rdma_rxe'
> + * is refused because of the references.
> + *
> + * For the global sockets in recv_sockets,
> + * we are sure that rxe_net_exit() will call
> + * rxe_release_udp_tunnel -> udp_tunnel_sock_release.
> + *
> + * So we don't need the additional reference to
> + * our own (THIS_MODULE).
> + */
> + sk_owner_put(sk);
> + /*
> + * We also call sk_owner_clear() otherwise
> + * sk_owner_put(sk) in sk_prot_free will
> + * fail, which is called via
> + * sk_free -> __sk_free -> sk_destruct
> + * and sk_destruct calls __sk_destruct
> + * directly or via call_rcu()
> + * so sk_prot_free() might be called
> + * after rxe_net_exit().
> + */
> + sk_owner_clear(sk);
> #endif /* CONFIG_DEBUG_LOCK_ALLOC */
> }
>
next prev parent reply other threads:[~2025-12-20 3:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 14:04 [PATCH] RDMA/rxe: let rxe_reclassify_recv_socket() call sk_owner_put() Stefan Metzmacher
2025-12-20 3:51 ` Zhu Yanjun [this message]
2025-12-20 13:05 ` Stefan Metzmacher
2025-12-20 23:05 ` Zhu Yanjun
2025-12-20 5:19 ` Shinichiro Kawasaki
2025-12-21 10:29 ` Leon Romanovsky
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=9ccc0635-7c0e-4a18-8469-9c5b6d9b268f@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=metze@samba.org \
--cc=netdev@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.com \
--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