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: Sat, 20 Dec 2025 15:05:43 -0800 [thread overview]
Message-ID: <8f623d8e-cd83-4610-83fa-794295576dac@linux.dev> (raw)
In-Reply-To: <01cd3f5a-2976-45ad-8a2d-32b3e39c6317@samba.org>
在 2025/12/20 5:05, Stefan Metzmacher 写道:
> Am 20.12.25 um 04:51 schrieb Zhu Yanjun:
>> 在 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.
>
> I don't think so, siw and the other place in rxe are attached to
> specific connections
> and there the reference is ok and needed.
Make sense. Thanks.
Yanjun.Zhu
>
> The problem was only related to the two global sockets with the lifetime
> the rdma_rxe is loaded.
>
> metze
--
Best Regards,
Yanjun.Zhu
next prev parent reply other threads:[~2025-12-20 23:05 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
2025-12-20 13:05 ` Stefan Metzmacher
2025-12-20 23:05 ` Zhu Yanjun [this message]
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=8f623d8e-cd83-4610-83fa-794295576dac@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