From: Greg KH <greg@kroah.com>
To: Rajani kantha <rajanikantha@engineer.com>
Cc: kees@ijzerbout.nl, baolu.lu@linux.intel.com, jroedel@suse.de,
stable@vger.kernel.org
Subject: Re: [PATCH 6.12.y] iommu/vt-d: Avoid use of NULL after WARN_ON_ONCE
Date: Wed, 2 Jul 2025 12:03:48 +0200 [thread overview]
Message-ID: <2025070233-unimpeded-reversion-ab61@gregkh> (raw)
In-Reply-To: <trinity-5b3af13a-3731-4b47-80a1-8ac7af67791f-1751424444098@3c-app-mailcom-lxa07>
On Wed, Jul 02, 2025 at 04:47:24AM +0200, Rajani kantha wrote:
> From: Kees Bakker <kees@ijzerbout.nl>
>
> [ Upstream commit 60f030f7418d3f1d94f2fb207fe3080e1844630b ]
>
> There is a WARN_ON_ONCE to catch an unlikely situation when
> domain_remove_dev_pasid can't find the `pasid`. In case it nevertheless
> happens we must avoid using a NULL pointer.
>
> Signed-off-by: Kees Bakker <kees@ijzerbout.nl>
> Link: https://lore.kernel.org/r/20241218201048.E544818E57E@bout3.ijzerbout.nl
> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
> Signed-off-by: Joerg Roedel <jroedel@suse.de>
> Signed-off-by: Rajani Kantha <rajanikantha@engineer.com>
> ---
> drivers/iommu/intel/iommu.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c
> index 56e9f125cda9..7c351274d004 100644
> --- a/drivers/iommu/intel/iommu.c
> +++ b/drivers/iommu/intel/iommu.c
> @@ -4306,13 +4306,14 @@ static void intel_iommu_remove_dev_pasid(struct device *dev, ioasid_t pasid,
> break;
> }
> }
> - WARN_ON_ONCE(!dev_pasid);
> spin_unlock_irqrestore(&dmar_domain->lock, flags);
>
> cache_tag_unassign_domain(dmar_domain, dev, pasid);
> domain_detach_iommu(dmar_domain, iommu);
> - intel_iommu_debugfs_remove_dev_pasid(dev_pasid);
> - kfree(dev_pasid);
> + if (!WARN_ON_ONCE(!dev_pasid)) {
> + intel_iommu_debugfs_remove_dev_pasid(dev_pasid);
> + kfree(dev_pasid);
> + }
> intel_pasid_tear_down_entry(iommu, dev, pasid, false);
> intel_drain_pasid_prq(dev, pasid);
> }
> --
> 2.34.1
>
Does not apply to the 6.12.y branch at all, what was this made against?
thanks,
greg k-h
prev parent reply other threads:[~2025-07-02 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 2:47 [PATCH 6.12.y] iommu/vt-d: Avoid use of NULL after WARN_ON_ONCE Rajani kantha
2025-07-02 10:03 ` Greg KH
2025-07-02 10:03 ` Greg KH [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=2025070233-unimpeded-reversion-ab61@gregkh \
--to=greg@kroah.com \
--cc=baolu.lu@linux.intel.com \
--cc=jroedel@suse.de \
--cc=kees@ijzerbout.nl \
--cc=rajanikantha@engineer.com \
--cc=stable@vger.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