From: Baolu Lu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Kevin Tian <kevin.tian@intel.com>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
stable@vger.kernel.org,
Nareshkumar Gollakoti <naresh.kumar.g@intel.com>
Subject: Re: [PATCH 1/1] iommu/vt-d: Avoid WARNING in sva unbind path
Date: Mon, 1 Jun 2026 13:25:29 +0800 [thread overview]
Message-ID: <b9696ee1-d502-463f-9925-f1a24fdcdbec@linux.intel.com> (raw)
In-Reply-To: <20260519052917.3729796-1-baolu.lu@linux.intel.com>
On 5/19/26 13:29, Lu Baolu wrote:
> The Intel IOMMU driver allows SVA on devices even if they do not support
> PCI/PRI. Commit 39c20c4e83b9 ("iommu/vt-d: Only handle IOPF for SVA when
> PRI is supported") modified the SVA bind path to allow this configuration
> by skipping IOPF enablement when PRI is missing. However, it failed to
> update the unbind path.
>
> This creates an imbalance: the unbind path attempts to disable IOPF for
> a device that never had it enabled, triggering a WARNING in
> intel_iommu_disable_iopf():
>
> WARNING: drivers/iommu/intel/iommu.c:3475 at intel_iommu_disable_iopf+0x4f/0x90d
> Call Trace:
> <TASK>
> blocking_domain_set_dev_pasid+0x50/0x70
> iommu_detach_device_pasid+0x89/0xc0
> iommu_sva_unbind_device+0x73/0x150
> xe_vm_close_and_put+0x4d2/0x1200 [xe]
>
> Fix this by bypassing IOPF operations for SVA domains on non-PRI hardware
> in both the bind and unbind paths.
>
> Fixes: 39c20c4e83b9 ("iommu/vt-d: Only handle IOPF for SVA when PRI is supported")
> Cc:stable@vger.kernel.org
> Reported-by: Nareshkumar Gollakoti<naresh.kumar.g@intel.com>
> Signed-off-by: Lu Baolu<baolu.lu@linux.intel.com>
> ---
> drivers/iommu/intel/iommu.h | 11 +++++++++++
> drivers/iommu/intel/svm.c | 12 ++++--------
> 2 files changed, 15 insertions(+), 8 deletions(-)
Queued for linux-next.
prev parent reply other threads:[~2026-06-01 5:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 5:29 Lu Baolu
2026-05-20 3:57 ` Tian, Kevin
2026-05-20 13:12 ` Yi Liu
2026-05-21 7:12 ` Baolu Lu
2026-06-01 5:25 ` Baolu Lu [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=b9696ee1-d502-463f-9925-f1a24fdcdbec@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.kumar.g@intel.com \
--cc=robin.murphy@arm.com \
--cc=stable@vger.kernel.org \
--cc=will@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
Powered by JetHome