linux-kernel - Re: [PATCH rdma-next] RDMA/core: release devices_rwsem when calling device

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] [day] [month] [year] [list]

Message-ID: <4ec19bf5-68da-4a6c-adcb-c8e127a7fcae@oracle.com>
Date: Mon, 26 Jan 2026 10:47:10 -0800
From: Sharath Srinivasan <sharath.srinivasan@...cle.com>
To: Leon Romanovsky <leon@...nel.org>, Jason Gunthorpe <jgg@...pe.ca>
Cc: Parav Pandit <parav@...dia.com>, linux-rdma@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH rdma-next] RDMA/core: release devices_rwsem when calling
 device_del

On 2026-01-25 5:47 a.m., Leon Romanovsky wrote:
> On Mon, Jan 19, 2026 at 03:53:29PM -0400, Jason Gunthorpe wrote:
>> On Mon, Jan 19, 2026 at 11:43:52AM -0800, Sharath Srinivasan wrote:
>>> The sync strategy in remove_all_compat_devs() can improved
>>> by adopting that of rdma_dev_exit_net() which releases devices_rwsem
>>> before calling remove_one_compat_dev()/device_del().
>>>
>>> Also fixes a comment typo in rdma_dev_exit_net().
>>
>> You cannot change this locking without writing a huge commit message
>> explaining in detail the reason why any change like this is safe..
> 
> We can drop this patch, it doesn't even apply.
> 
> Thanks
> 

Thanks for trying. I'll send a rebased-v2 with an expanded commit message as Jason suggested.

Regards,
Sharath

>>
>> Jason
>>
>