linux-kernel - Re: [PATCH] driver core: fix inverted "locked" suffix of driver_match

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: <DG3Y4E41QIZA.3LBI0AN3JIDCN@kernel.org>
Date: Sun, 01 Feb 2026 22:33:46 +0100
From: "Danilo Krummrich" <dakr@...nel.org>
To: <gregkh@...uxfoundation.org>, <rafael@...nel.org>,
 <hanguidong02@...il.com>
Cc: <driver-core@...ts.linux.dev>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] driver core: fix inverted "locked" suffix of
 driver_match_device()

On Sat Jan 31, 2026 at 2:42 AM CET, Danilo Krummrich wrote:
> In the current implementation driver_match_device() expects the device
> lock to be held, while driver_match_device_locked() acquires the device
> lock.
>
> By convention it should be the other way around, hence swap the name of
> both functions.
>
> Fixes: dc23806a7c47 ("driver core: enforce device_lock for driver_match_device()")
> Signed-off-by: Danilo Krummrich <dakr@...nel.org>

Applied to driver-core-testing, thanks!