linux-kernel - Re: [PATCH 1/1] iommu/vt-d: Add a quirk flag for scope mismatched devices

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

Date:   Tue, 24 Dec 2019 12:08:57 -0700
From:   Jerry Snitselaar <jsnitsel@...hat.com>
To:     Lu Baolu <baolu.lu@...ux.intel.com>
Cc:     Joerg Roedel <joro@...tes.org>,
        Roland Dreier <roland@...estorage.com>,
        Jim Yan <jimyan@...du.com>, iommu@...ts.linux-foundation.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] iommu/vt-d: Add a quirk flag for scope mismatched
 devices

On Tue Dec 24 19, Lu Baolu wrote:
>We expect devices with endpoint scope to have normal PCI headers,
>and devices with bridge scope to have bridge PCI headers.  However
>Some PCI devices may be listed in the DMAR table with bridge scope,
>even though they have a normal PCI header. Add a quirk flag for
>those special devices.
>
>Cc: Roland Dreier <roland@...estorage.com>
>Cc: Jim Yan <jimyan@...du.com>
>Signed-off-by: Lu Baolu <baolu.lu@...ux.intel.com>
>---

Reviewed-by: Jerry Snitselaar <jsnitsel@...hat.com>