linux-kernel - Re: [PATCH] iommu/vt-d: Fix IOMMU lookup for VF's

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1477829406.4154.2.camel@infradead.org>
Date:   Sun, 30 Oct 2016 06:10:06 -0600
From:   David Woodhouse <dwmw2@...radead.org>
To:     Ashok Raj <ashok.raj@...el.com>, linux-kernel@...r.kernel.org
Cc:     Joerg Roedel <joro@...tes.org>,
        Sainath Grandhi <sainath.grandhi@...el.com>,
        iommu@...ts.linux-foundation.org, stable@...r.kernel.org
Subject: Re: [PATCH] iommu/vt-d: Fix IOMMU lookup for VF's

On Fri, 2016-10-21 at 15:32 -0700, Ashok Raj wrote:
> IOMMU driver must pick the same IOMMU as that of a Physical Function (PF) for
> any of its Virtual Functions (VF). It is not practical to list all the VF's
> in the DMAR scope, as this list could be quite large. Linux also ignores any
> VF's listed in DMAR. See dmar_pci_bus_notifier() for virtfn handling.
> 
> Since the driver is looking for the bdf of the VF, it will not find one from
> searching the DRHD listed in BIOS.  As a result, the IOMMU driver associates
> the VF's under the INCLUDE_ALL iommu incorrectly.
> 
> This patch looks up the IOMMU of the PF when handling VF's.

I've made some cosmetic fixes — adding comments, and tweaking the
commit comment — and applied this to my tree. Thanks.

-- 
dwmw2



Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (5760 bytes)