From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: Andreas Noever <andreas.noever@gmail.com>,
Mika Westerberg <westeri@kernel.org>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
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 13:31:13 +0200 [thread overview]
Message-ID: <20260807113113.GO235112@black.igk.intel.com> (raw)
In-Reply-To: <7510bf11-7ae3-47dc-b499-5eb5e0aa0192@yandex.ru>
On Fri, Aug 07, 2026 at 02:13:06PM +0300, Dmitry Antipov wrote:
> On 8/7/26 12:58 PM, Mika Westerberg wrote:
>
> > Yeah, I'm not entirely sure we want to start "fixing" issues like these
> > where it's clearly not a USB4/TB NHI. IMHO If user forces the driver
> > somehow to bind to this unrelated device then she/he got what asked for.
>
> I agree but isn't there a scenario to trigger such a weird probe just by mistake?
Okay but how it is "mistake"? ;-) I'm actually not sure how this was even
triggered. Something like you as root echo random PCI device name to "bind"
files of a driver?
next prev parent reply other threads:[~2026-08-07 11:31 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 [this message]
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
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=20260807113113.GO235112@black.igk.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=dmantipov@yandex.ru \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox