From: Greg KH <gregkh@linuxfoundation.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: syzbot <syzbot@kernel.org>,
syzkaller-bugs@googlegroups.com, Marco Elver <elver@google.com>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
Andreas Noever <andreas.noever@gmail.com>,
linux-usb@vger.kernel.org, Mika Westerberg <westeri@kernel.org>,
linux-kernel@vger.kernel.org, syzbot@lists.linux.dev
Subject: Re: [PATCH] thunderbolt: Validate BAR 0 resource type and size
Date: Wed, 26 Aug 2026 08:08:48 +0200 [thread overview]
Message-ID: <2026082622-bunkmate-bleep-6716@gregkh> (raw)
In-Reply-To: <20260826043929.GM893316@black.igk.intel.com>
On Wed, Aug 26, 2026 at 06:39:29AM +0200, Mika Westerberg wrote:
> Hi,
>
> On Tue, Aug 25, 2026 at 04:09:37PM +0000, syzbot wrote:
> > From: Marco Elver <elver@google.com>
> >
> > The thunderbolt driver can crash with a page fault if it binds to an
> > arbitrary PCI device (e.g., via sysfs driver_override) that has an I/O port
> > BAR at index 0 instead of an MMIO BAR.
>
> Well, if you bind it to a random PCIe device you get what you asked for.
> This is specifically the reason we have the PCI IDs and the like in the
> drivers. Anything outside of that you need to know what you are doing.
>
And again, I keep telling the syzbot people that this is not a valid
thing to care about...
prev parent reply other threads:[~2026-08-26 6:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 16:09 [PATCH] thunderbolt: Validate BAR 0 resource type and size syzbot
2026-08-26 4:39 ` Mika Westerberg
2026-08-26 6:08 ` Greg KH [this message]
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=2026082622-bunkmate-bleep-6716@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=elver@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=syzbot@kernel.org \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.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