linux-kernel - Re: [PATCH] driver core: Fix concurrency issue in match driver interface.

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: <2024111257-diabetic-parsley-84e9@gregkh>
Date: Tue, 12 Nov 2024 20:02:44 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Qiu-ji Chen <chenqiuji666@...il.com>
Cc: rafael@...nel.org, linux-kernel@...r.kernel.org, baijiaju1990@...il.com
Subject: Re: [PATCH] driver core: Fix concurrency issue in match driver
 interface.

On Wed, Nov 13, 2024 at 02:21:57AM +0800, Qiu-ji Chen wrote:
> Hi, Greg
> 
> The driver_override is updated by driver_set_override(), a function
> provided by the driver core. In driver_set_override(), the
> driver_override is updated while holding the device_lock. Therefore,
> locking is required when calling match to prevent the driver_override
> from being modified within driver_set_override().

I'm sorry, but I lost all context.  What are you referring to here?

Remember, some of use get 1000+ emails a day to do something with,
always respond with proper quoting and response in order to have a
conversation that everyone can understand.

thanks,

greg k-h