linux-kernel - Re: [PATCH] gpio: omap: do not register driver in probe()

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

Message-Id: <DFW0HVK6AF0G.TW6R157R8O27@kernel.org>
Date: Fri, 23 Jan 2026 14:44:06 +0100
From: "Danilo Krummrich" <dakr@...nel.org>
To: <gregkh@...uxfoundation.org>, <rafael@...nel.org>, <broonie@...nel.org>,
 <will@...nel.org>, <grygorii.strashko@...com>, <ssantosh@...nel.org>,
 <khilman@...nel.org>, <linusw@...nel.org>, <brgl@...nel.org>
Cc: <driver-core@...ts.linux.dev>, <linux-kernel@...r.kernel.org>,
 <linux-omap@...r.kernel.org>, <linux-gpio@...r.kernel.org>, "Danilo
 Krummrich" <dakr@...nel.org>
Subject: Re: [PATCH] gpio: omap: do not register driver in probe()

On Fri Jan 23, 2026 at 2:31 PM CET, Danilo Krummrich wrote:
> However, for the purpose of avoiding the described potential deadlock in
> combination with commit dc23806a7c47 ("driver core: enforce device_lock for
> driver_match_device()"), this patch only addresses the driver registration
> issue.

I.e. unless there are any concerns, I'd like to take this one through the
driver-core tree.