linux-kernel - Re: [PATCH v1] iommu: Avoid use of NULL after WARN_ON

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Z2KJEUdGD_DFq_Xl@8bytes.org>
Date: Wed, 18 Dec 2024 09:34:25 +0100
From: Joerg Roedel <joro@...tes.org>
To: Kees Bakker <kees@...erbout.nl>
Cc: Baolu Lu <baolu.lu@...ux.intel.com>, iommu@...ts.linux.dev,
	Tian Kevin <kevin.tian@...el.com>, Will Deacon <will@...nel.org>,
	Robin Murphy <robin.murphy@....com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] iommu: Avoid use of NULL after WARN_ON_ONCE

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@...erbout.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.