All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
	Andreas Noever <andreas.noever@gmail.com>,
	Mika Westerberg <westeri@kernel.org>,
	Yehezkel Bernat <YehezkelShB@gmail.com>,
	linux-usb@vger.kernel.org, lvc-project@linuxtesting.org,
	syzbot+901ca72278dfd89daf58@syzkaller.appspotmail.com
Subject: Re: [PATCH] thunderbolt: verify PCI resource type and size in nhi_probe()
Date: Fri, 7 Aug 2026 15:11:32 +0200	[thread overview]
Message-ID: <2026080747-doing-humongous-c14b@gregkh> (raw)
In-Reply-To: <0c4957c9-8642-449d-b71e-6615babd553f@yandex.ru>

On Fri, Aug 07, 2026 at 02:47:54PM +0300, Dmitry Antipov wrote:
> On 8/7/26 2:31 PM, Mika Westerberg wrote:
> 
> > I'm actually not sure how this was even triggered
> 
> :-) just as documented in https://docs.kernel.org/driver-api/driver-model/binding.html:
> 
> Userspace may override the standard matching by writing a driver name to a device’s
> driver_override sysfs attribute. When set, only a driver whose name matches the
> override will be considered during binding. This bypasses all bus-specific matching
> (OF, ACPI, ID tables, etc.).

Yes, and anyone who uses this, gets to keep the broken pieces of the
kernel if they attempt to bind a driver to a device that can't actually
support it.

This is a debugging-only feature, don't treat it as something for which
EVERY driver would have to somehow insulate themselves from.  That's not
what this is for at all.

thanks,

greg k-h

  parent reply	other threads:[~2026-08-07 13:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07  8:37 [PATCH] thunderbolt: verify PCI resource type and size in nhi_probe() Dmitry Antipov
2026-08-07  9:58 ` Mika Westerberg
2026-08-07 11:13   ` Dmitry Antipov
2026-08-07 11:31     ` Mika Westerberg
2026-08-07 11:47       ` Dmitry Antipov
2026-08-07 12:01         ` Mika Westerberg
2026-08-07 12:36           ` Dmitry Antipov
2026-08-07 13:05             ` Mika Westerberg
2026-08-07 13:11         ` Greg Kroah-Hartman [this message]
2026-08-07 13:27           ` Dmitry Antipov
2026-08-07 13:59             ` Greg Kroah-Hartman

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=2026080747-doing-humongous-c14b@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=dmantipov@yandex.ru \
    --cc=linux-usb@vger.kernel.org \
    --cc=lvc-project@linuxtesting.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=syzbot+901ca72278dfd89daf58@syzkaller.appspotmail.com \
    --cc=westeri@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.