From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A68851E0E08 for ; Tue, 8 Oct 2024 16:37:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.175.65.16 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1728405458; cv=none; b=USduHCo0GFVtJCVHhB67+ALXdl6syj55NwFvpRNd6yzQhWKBaMm36hogHOcW8KVgn8n95oGI9OIIpuqXS20T6gkhIoRUDCwu6VoY4NqIfTHVUyevap/KYIODc7GUbaTMNuGFKJU/y1H4HKIxb6y/T4Q0iH20Ocohe2x/cZ4kSLs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1728405458; c=relaxed/simple; bh=rIsDvpg79JVMANiUS0HeTzawj6o7FRI+dARbdd2NWQE=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=XnFcY8q/y5p9wUlDlWG4sd9l4IFoLeyiEEo488B0O6fSb0J6zROLqeGanTfqQV2nCbmW1l1eYm2AAVHRqqFpNSiFltOaZxjr8XCPeLL8eKCqvJgbGcTCuNU1iRZfzFdYXjEUKFP/RGMcRebV25sXwwV8ybHt9ce0WpcFHuG9d0Q= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=none smtp.mailfrom=linux.intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=SXSjaPcK; arc=none smtp.client-ip=198.175.65.16 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="SXSjaPcK" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1728405457; x=1759941457; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=rIsDvpg79JVMANiUS0HeTzawj6o7FRI+dARbdd2NWQE=; b=SXSjaPcKAVg32CUTg/BOMNvnle6fedij+4CsqreGH1gCA8O9yH4wPqZ3 R22xyfwVa/1Pg37Lzabbyv2zc8r3mDhLddKTTbOf3xG6Ewq+2QecQCd7k JyVtDU5Nc+6el+SdAxxTpzpRX8Ey+ZnS3gmprV1Gyffzwc8XibNF1GRUm hND4A1VNTmdWZPvgvLsCla2nmP4XC1huO9erfQq1C5NcNKcJ0OATCytc/ oFmIMcAHzGKonSiuahRkl+4vtgWSyuibkCSLKL1jXYhtGcQboqwLT+DAd 2c93XVU8dyrqpprfMl1kZ0OCrDVkl0yZC426GsU/7rtybAZts7Zyn1NC+ w==; X-CSE-ConnectionGUID: kOkdsU8dQ1iodH1/GsulWA== X-CSE-MsgGUID: Ke8lBeJ6RRaWBimi+/0vrg== X-IronPort-AV: E=McAfee;i="6700,10204,11219"; a="27711989" X-IronPort-AV: E=Sophos;i="6.11,187,1725346800"; d="scan'208";a="27711989" Received: from orviesa004.jf.intel.com ([10.64.159.144]) by orvoesa108.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Oct 2024 09:37:36 -0700 X-CSE-ConnectionGUID: /6PxXlIqRGqjAoKiySfI1w== X-CSE-MsgGUID: GcaT686cRQm+gN+qUL9PUg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.11,187,1725346800"; d="scan'208";a="80926966" Received: from black.fi.intel.com ([10.237.72.28]) by orviesa004.jf.intel.com with ESMTP; 08 Oct 2024 09:37:34 -0700 Received: by black.fi.intel.com (Postfix, from userid 1001) id D0AD920F; Tue, 08 Oct 2024 19:37:32 +0300 (EEST) Date: Tue, 8 Oct 2024 19:37:32 +0300 From: "mika.westerberg@linux.intel.com" To: Lukas Wunner Cc: "Wassenberg, Dennis" , "kbusch@kernel.org" , "ilpo.jarvinen@linux.intel.com" , "linux-pci@vger.kernel.org" , "mpearson-lenovo@squebb.ca" , "Jonathan.Cameron@huawei.com" , "minipli@grsecurity.net" Subject: Re: UAF during boot on MTL based devices with attached dock Message-ID: <20241008163732.GT275077@black.fi.intel.com> References: <6de4b45ff2b32dd91a805ec02ec8ec73ef411bf6.camel@secunet.com> <68de3ca4-a624-8b02-8f6d-889deb61495d@linux.intel.com> <233b9645e201556422dea79f71262d115c687fcb.camel@secunet.com> Precedence: bulk X-Mailing-List: linux-pci@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: 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.