From: Joerg Roedel <joro@8bytes.org>
To: Kees Bakker <kees@ijzerbout.nl>
Cc: Baolu Lu <baolu.lu@linux.intel.com>,
iommu@lists.linux.dev, Tian Kevin <kevin.tian@intel.com>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] iommu: Avoid use of NULL after WARN_ON_ONCE
Date: Wed, 18 Dec 2024 09:34:25 +0100 [thread overview]
Message-ID: <Z2KJEUdGD_DFq_Xl@8bytes.org> (raw)
In-Reply-To: <20241115190316.28A6B18DFF2@bout3.ijzerbout.nl>
On Fri, Nov 15, 2024 at 07:46:25PM +0100, Kees Bakker wrote:
> 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>
> ---
> drivers/iommu/intel/iommu.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
This patch is Intel VT-d specific, please use the 'iommu/vt-d:' prefix
in the subject line.
prev parent reply other threads:[~2024-12-18 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 18:46 [PATCH v1] iommu: Avoid use of NULL after WARN_ON_ONCE Kees Bakker
2024-12-18 8:34 ` Joerg Roedel [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=Z2KJEUdGD_DFq_Xl@8bytes.org \
--to=joro@8bytes.org \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=kees@ijzerbout.nl \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.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