All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Danilo Krummrich <dakr@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	driver-core@lists.linux.dev, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] driver core: reject devices with unregistered buses
Date: Wed, 29 Apr 2026 18:00:08 +0200	[thread overview]
Message-ID: <afIrCO3QSL3hx10S@hovoldconsulting.com> (raw)
In-Reply-To: <DI5QUINEJC6U.32I161SD0KU76@kernel.org>

On Wed, Apr 29, 2026 at 05:29:02PM +0200, Danilo Krummrich wrote:
> On Wed Apr 29, 2026 at 5:08 PM CEST, Johan Hovold wrote:
> > No, I'm saying that it's a bug in driver core to silently treat a device
> > that is registered before its bus as a bus-less device.
> 
> This is an argument that I can buy into, but in the previous discussion (and in
> the commit message) the whole motivation evolved around "reject devices with
> unregistered buses to catch any callers that get the ordering wrong", i.e. catch
> other people's bugs.
>
> What you are raising now is "the driver core is conflating no bus with
> unregistered bus handling". However, the commit message does not reflect that at
> all.

The commit message already explains the issue:

	Trying to register a device on a bus which has not yet been
	registered used to trigger a NULL-pointer dereference, but since
	the const bus structure rework registration instead succeeds
	without the device being added to the bus.

namely that

	 registration [...] succeeds [but] without the device being
	 added to the bus.

> Can you please adjust the commit message accordingly?

Perhaps I can add "(i.e. as if it were a bus-less device)" to stress it
more but I'm not sure it's needed.

Johan

  reply	other threads:[~2026-04-29 16:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 10:28 [PATCH] driver core: reject devices with unregistered buses Johan Hovold
2026-04-28 19:09 ` Danilo Krummrich
2026-04-29 10:11   ` Johan Hovold
2026-04-29 11:11     ` Danilo Krummrich
2026-04-29 11:33       ` Johan Hovold
2026-04-29 14:52         ` Danilo Krummrich
2026-04-29 15:08           ` Johan Hovold
2026-04-29 15:29             ` Danilo Krummrich
2026-04-29 16:00               ` Johan Hovold [this message]
2026-04-29 16:18                 ` Danilo Krummrich

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=afIrCO3QSL3hx10S@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=dakr@kernel.org \
    --cc=driver-core@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=stable@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.