linux-kernel - Re: [PATCH v2] vfio/pci: Mask buggy SR-IOV VF INTx support

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: <20180921091617.07a96af5@t450s.home>
Date:   Fri, 21 Sep 2018 09:16:17 -0600
From:   Alex Williamson <alex.williamson@...hat.com>
To:     Christoph Hellwig <hch@...radead.org>
Cc:     kvm@...r.kernel.org, ashok.raj@...el.com, gage.eads@...el.com,
        gnomes@...rguk.ukuu.org.uk, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] vfio/pci: Mask buggy SR-IOV VF INTx support

On Thu, 20 Sep 2018 22:53:04 -0700
Christoph Hellwig <hch@...radead.org> wrote:

> > +/*
> > + * Nag about hardware bugs, hopefully to have vendors fix them, but at least
> > + * to collect a list of dependencies for the VF INTx pin quirk below.
> > + */
> > +static const struct pci_device_id known_bogus_vf_intx_pin[] = {
> > +	{ PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0x270c) },
> > +	{}
> > +};  
> 
> What device is this? We don't have the device ID anywhere, so I guess
> it is something match by the class code?

Intel hasn't disclosed the device yet, so we don't know that there's an
existing driver at all for it.  Thanks,

Alex