From: "Uwe Kleine-König" <ukleinek@kernel.org>
To: Thierry Reding <thierry.reding@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
driver-core@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-pwm@vger.kernel.org, linux-tegra@vger.kernel.org,
Thierry Reding <treding@nvidia.com>,
Richard Weinberger <richard@nod.at>
Subject: Re: [PATCH 1/2] driver: core: Allow drivers to opt out of driver_override
Date: Fri, 25 Sep 2026 19:21:02 +0200 [thread overview]
Message-ID: <araoY6u_A9Odej-G@monoceros> (raw)
In-Reply-To: <arKLt__frMjzSA4t@orome>
[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]
Hello Thierry,
On Tue, Sep 22, 2026 at 04:09:25PM +0200, Thierry Reding wrote:
> > Having said that I think there is only a handful of drivers that are
> > actually supposed to work when used in a driver override (vfio stuff,
> > spidev and i2c-dev come to mind), so I'd prefer that drivers opt-in
> > instead of opt-out. Otherwise we yet another flag that drivers should
> > set in general but don't because driver authors are not aware[1]. The
> > few drivers that rely on driver overriding should be identified quickly,
> > and if we miss one that doesn't result in a way to make the kernel oops.
>
> We could easily invert the logic in this patch to make this opt-in, but
> it might be difficult to know exactly which ones want to opt-in, given
> it's been enabled by default for a really long time.
I'd have the heart to do that in combination with a kernel parameter
that allows to drop the strictness (and remove that after some time).
Currently the only driver I'm aware of that is supposed to be used with
driver_override is drivers/spi/spidev.c. AFAICT the i2c equivalent
doesn't need driver overriding (as it attaches to a bus instead of an
individual device) and vfio seems to work without overrides.
I'm sure I missed some driver, but these can easily get fixed when users
start wailing.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-09-25 17:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 11:38 [PATCH 0/2] driver: core: Allow drivers to opt out of driver_override Thierry Reding
2026-09-22 11:38 ` [PATCH 1/2] " Thierry Reding
2026-09-22 12:13 ` Greg Kroah-Hartman
2026-09-22 12:49 ` Danilo Krummrich
2026-09-22 13:17 ` Uwe Kleine-König
2026-09-22 14:09 ` Thierry Reding
2026-09-25 17:21 ` Uwe Kleine-König [this message]
2026-09-22 11:38 ` [PATCH 2/2] pwm: tegra: Opt " Thierry Reding
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=araoY6u_A9Odej-G@monoceros \
--to=ukleinek@kernel.org \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=richard@nod.at \
--cc=thierry.reding@kernel.org \
--cc=treding@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox