From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 62858430BA3; Sun, 1 Mar 2026 01:22:46 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772328166; cv=none; b=nMhGYu9XrbWimegQqQi7fX/qoDTfnUq34+JspIfjXhO+BKwGBct4gLx+heVBL7YpsQ2JVBCo53V2kcj6g1OyFwJFLCtz7TeM7AEeYcUaZzIWVXNcoiKlW77eQF5A0Ewjs4ny8ATcIcFYjMVorRHZeSEPE0c6NbVhEdqYug4TzVs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772328166; c=relaxed/simple; bh=+ROLhv8WM+oN45TbQKg3sKmN5USgWb2m1qHlpVQp6DU=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type; b=EDNjtGf9zamcJ46YkKioryclCWNf97iGlYdwnfbV5lDHXDwmKJ4FjEKWcg81t5jM39aUI2A4FTaNNaPoQ6VatA5uI9c4hBm8vjAyfc+86JJu8V7cWyvlvU6Bu8dzwJNK33MbaNz8CkFsjxVEdT8zygxO3gNFKCqtndDTV6HzeQM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=BE5iyPPq; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="BE5iyPPq" Received: by smtp.kernel.org (Postfix) with ESMTPSA id B1F1EC19421; Sun, 1 Mar 2026 01:22:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1772328166; bh=+ROLhv8WM+oN45TbQKg3sKmN5USgWb2m1qHlpVQp6DU=; h=From:To:Cc:Subject:Date:From; b=BE5iyPPq10l33/UCpUj9hylINPaAXE4phIReXeBLaHmZYT6fmnqLXCL74mQ3gy2+t cLcpos8fvZMeVvo1ckVMJrTbiq3C/LW6bpmRo6tYg+dovUK8kK+lpuKMGDMwV06f9b UijD5Mwsln2/54S6hrCwIVzUZX61NUi27NOG8acg1SOnhY4NNWWlTYDkLXTGXQD3Eg lYYv9+LlpMewfXqYc+0XHGWT+uMpKXQBLOp0be62ULIokERFA3Sb2ei6tYD5JCeOUg uzFVEnBRkXp6xPumJ+nH6RGtNlJOSmwm4X58SwhnI843FOItkjXfykO3hnpw33x94t b+qGVVUcHux2g== From: Sasha Levin To: stable@vger.kernel.org, guojinhui.liam@bytedance.com Cc: Lu Baolu , Joerg Roedel , iommu@lists.linux.dev Subject: FAILED: Patch "iommu/vt-d: Flush dev-IOTLB only when PCIe device is accessible in scalable mode" failed to apply to 6.12-stable tree Date: Sat, 28 Feb 2026 20:22:44 -0500 Message-ID: <20260301012244.1679211-1-sashal@kernel.org> X-Mailer: git-send-email 2.51.0 Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Patchwork-Hint: ignore X-stable: review Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The patch below does not apply to the 6.12-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to . Thanks, Sasha ------------------ original commit in Linus's tree ------------------ >From 10e60d87813989e20eac1f3eda30b3bae461e7f9 Mon Sep 17 00:00:00 2001 From: Jinhui Guo Date: Thu, 22 Jan 2026 09:48:51 +0800 Subject: [PATCH] iommu/vt-d: Flush dev-IOTLB only when PCIe device is accessible in scalable mode MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Commit 4fc82cd907ac ("iommu/vt-d: Don't issue ATS Invalidation request when device is disconnected") relies on pci_dev_is_disconnected() to skip ATS invalidation for safely-removed devices, but it does not cover link-down caused by faults, which can still hard-lock the system. For example, if a VM fails to connect to the PCIe device, "virsh destroy" is executed to release resources and isolate the fault, but a hard-lockup occurs while releasing the group fd. Call Trace: qi_submit_sync qi_flush_dev_iotlb intel_pasid_tear_down_entry device_block_translation blocking_domain_attach_dev __iommu_attach_device __iommu_device_set_domain __iommu_group_set_domain_internal iommu_detach_group vfio_iommu_type1_detach_group vfio_group_detach_container vfio_group_fops_release __fput Although pci_device_is_present() is slower than pci_dev_is_disconnected(), it still takes only ~70 µs on a ConnectX-5 (8 GT/s, x2) and becomes even faster as PCIe speed and width increase. Besides, devtlb_invalidation_with_pasid() is called only in the paths below, which are far less frequent than memory map/unmap. 1. mm-struct release 2. {attach,release}_dev 3. set/remove PASID 4. dirty-tracking setup The gain in system stability far outweighs the negligible cost of using pci_device_is_present() instead of pci_dev_is_disconnected() to decide when to skip ATS invalidation, especially under GDR high-load conditions. Fixes: 4fc82cd907ac ("iommu/vt-d: Don't issue ATS Invalidation request when device is disconnected") Cc: stable@vger.kernel.org Signed-off-by: Jinhui Guo Link: https://lore.kernel.org/r/20251211035946.2071-3-guojinhui.liam@bytedance.com Signed-off-by: Lu Baolu Signed-off-by: Joerg Roedel --- drivers/iommu/intel/pasid.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/iommu/intel/pasid.c b/drivers/iommu/intel/pasid.c index 3f6d78180d799..99692f88b8834 100644 --- a/drivers/iommu/intel/pasid.c +++ b/drivers/iommu/intel/pasid.c @@ -218,7 +218,7 @@ devtlb_invalidation_with_pasid(struct intel_iommu *iommu, if (!info || !info->ats_enabled) return; - if (pci_dev_is_disconnected(to_pci_dev(dev))) + if (!pci_device_is_present(to_pci_dev(dev))) return; sid = PCI_DEVID(info->bus, info->devfn); -- 2.51.0