All of lore.kernel.org
 help / color / mirror / Atom feed
From: "yanjun.zhu" <yanjun.zhu@linux.dev>
To: Stefan Metzmacher <metze@samba.org>,
	Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Cc: Leon Romanovsky <leon@kernel.org>
Subject: Re: [bug report] rdma_rxe module unload failure with DEBUG_LOCK_ALLOC enabled
Date: Fri, 19 Dec 2025 09:59:21 -0800	[thread overview]
Message-ID: <70fbec5d-1894-4660-a768-62e176e9e421@linux.dev> (raw)
In-Reply-To: <7affc986-1378-4257-bac6-cd0be4e2f5c8@samba.org>

On 12/19/25 5:45 AM, Stefan Metzmacher wrote:
> Hi Shinichiro,
> 
>> While I evaluate v6.19-rc1 kernel, I found that rdma_rxe module unload 
>> fails.
>> The failure can be recreated by simple two commands below:
>>
>>     $ sudo modprobe rdma_rxe
>>     $ sudo modprobe -r rdma_rxe
>>     modprobe: FATAL: Module rdma_rxe is in use.
>>
>> I bisected and found the trigger commit is this:
>>
>>     80a85a771deb ("RDMA/rxe: reclassify sockets in order to avoid 
>> false positives from lockdep")

Thanks a lot.

https://git.samba.org/?p=metze/linux/wip.git;a=commitdiff;h=7f55eb3373dca97b706e8521705a06d4bf84b0f0

Hi, Shinichiro Kawasaki

Please confirm if the above link can fix the above problem or not.

Best Regards,
Yanjun.Zhu

>>
>> This commit changes the driver behavior when the kconfig 
>> DEBUG_LOCK_ALLOC is
>> enabled, and my kconfig does so.
>>
>> Actions for fix will be appreciated.
> 
> I have a fix for this, see:
> https://git.samba.org/?p=metze/linux/ 
> wip.git;a=commitdiff;h=7f55eb3373dca97b706e8521705a06d4bf84b0f0
> 
> I'll post it to the list later today.
> 
> Sorry for the trouble!
> metze


  reply	other threads:[~2025-12-19 17:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-19 11:29 [bug report] rdma_rxe module unload failure with DEBUG_LOCK_ALLOC enabled Shinichiro Kawasaki
2025-12-19 13:45 ` Stefan Metzmacher
2025-12-19 17:59   ` yanjun.zhu [this message]
2025-12-20  5:22     ` Shinichiro Kawasaki

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=70fbec5d-1894-4660-a768-62e176e9e421@linux.dev \
    --to=yanjun.zhu@linux.dev \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=metze@samba.org \
    --cc=shinichiro.kawasaki@wdc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.