From: Vasant Hegde <vasant.hegde@amd.com>
To: Wentao Liang <vulab@iscas.ac.cn>, iommu@lists.linux.dev
Cc: jgg@ziepe.ca, joro@8bytes.org, linux-kernel@vger.kernel.org,
robin.murphy@arm.com, suravee.suthikulpanit@amd.com,
wei.huang2@amd.com, will@kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] iommu/amd: Fix PCI device reference leak in iommu_call_iopf_notifier()
Date: Wed, 30 Sep 2026 15:28:50 +0530 [thread overview]
Message-ID: <214ea1d6-8b3a-4d8f-b0f2-e2f1de9d5632@amd.com> (raw)
In-Reply-To: <20260916185804.2093996-1-vulab@iscas.ac.cn>
On 9/17/2026 12:28 AM, Wentao Liang wrote:
> pci_get_domain_bus_and_slot() returns a PCI device with an elevated
> reference count, but iommu_call_iopf_notifier() never drops it, neither
> when the page request has been reported nor on the abort path.
>
> Put the device reference on both exits.
Its already addressed by commit af3b69b16383.
-Vasant
prev parent reply other threads:[~2026-09-30 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 18:58 Wentao Liang
2026-09-30 9:58 ` Vasant Hegde [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=214ea1d6-8b3a-4d8f-b0f2-e2f1de9d5632@amd.com \
--to=vasant.hegde@amd.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=stable@vger.kernel.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=vulab@iscas.ac.cn \
--cc=wei.huang2@amd.com \
--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
all inboxes | Powered by JetHome®