From: "mika.westerberg@linux.intel.com" <mika.westerberg@linux.intel.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: "Wassenberg, Dennis" <Dennis.Wassenberg@secunet.com>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"ilpo.jarvinen@linux.intel.com" <ilpo.jarvinen@linux.intel.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"mpearson-lenovo@squebb.ca" <mpearson-lenovo@squebb.ca>,
"Jonathan.Cameron@huawei.com" <Jonathan.Cameron@huawei.com>,
"minipli@grsecurity.net" <minipli@grsecurity.net>
Subject: Re: UAF during boot on MTL based devices with attached dock
Date: Tue, 8 Oct 2024 19:37:32 +0300 [thread overview]
Message-ID: <20241008163732.GT275077@black.fi.intel.com> (raw)
In-Reply-To: <ZwU6ijD8I5hzMv9X@wunner.de>
On Tue, Oct 08, 2024 at 03:58:34PM +0200, Lukas Wunner wrote:
> Finally, I'd appreciate if you could send me dmesg output with the
> refcounting fix applied. As said before, the MTL Thunderbolt controller
> claims that the link and slot presence bits are cleared, so it
> de-enumerates everything attached via Thunderbolt. I'm wondering
> if it then re-enumerates the Thunderbolt-attached devices so they're
> actually usable?
>
> I'm hoping Mika can clarify with Intel Thunderbolt CoE whether this
> is a hardware issue in MTL that can e.g. be fixed through a firmware
> or BIOS update.
I think here it happens because we reset the host router when the driver
probes so all the BIOS CM created tunnels will be torn down as well.
next prev parent reply other threads:[~2024-10-08 16:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 8:06 UAF during boot on MTL based devices with attached dock Wassenberg, Dennis
2024-09-21 9:08 ` Ilpo Järvinen
2024-09-23 8:38 ` Wassenberg, Dennis
2024-09-23 4:41 ` mika.westerberg
2024-09-23 8:43 ` Wassenberg, Dennis
2024-09-23 11:17 ` mika.westerberg
2024-09-23 13:42 ` Wassenberg, Dennis
2024-09-23 12:23 ` Wassenberg, Dennis
2024-09-24 10:51 ` Ilpo Järvinen
2024-09-25 15:38 ` Wassenberg, Dennis
2024-09-26 13:58 ` Ilpo Järvinen
2024-10-07 16:34 ` Wassenberg, Dennis
2024-10-03 13:46 ` Lukas Wunner
2024-10-04 7:45 ` Lukas Wunner
2024-10-07 16:49 ` Wassenberg, Dennis
2024-10-08 13:58 ` Lukas Wunner
2024-10-08 16:37 ` mika.westerberg [this message]
2024-10-08 18:23 ` Lukas Wunner
2024-10-09 4:44 ` mika.westerberg
2024-10-09 11:47 ` Lukas Wunner
2024-10-09 12:55 ` mika.westerberg
2024-10-09 6:26 ` Wassenberg, Dennis
2024-10-07 16:20 ` Wassenberg, Dennis
2024-09-24 8:54 ` Lukas Wunner
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=20241008163732.GT275077@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=Dennis.Wassenberg@secunet.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kbusch@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=minipli@grsecurity.net \
--cc=mpearson-lenovo@squebb.ca \
/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