linux-kernel - Re: [PATCH] iommu:Check that iommu_device_create has completed successfully in alloc

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20160104163816.GS18805@8bytes.org>
Date:	Mon, 4 Jan 2016 17:38:16 +0100
From:	Joerg Roedel <joro@...tes.org>
To:	Nicholas Krause <xerofoify@...il.com>
Cc:	iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] iommu:Check that iommu_device_create has completed
 successfully in alloc_iommu

On Mon, Jan 04, 2016 at 11:27:10AM -0500, Nicholas Krause wrote:
> Yes that's true and was wondering if you want me to fix it up to set
> the pointer back to null first or if preferred around safe state. 

The best solution is to set the dmar->iommu pointer after the error
check for iommu_device_create().



	Joerg

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/