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
| ||
|
Date: Thu, 9 Aug 2018 16:03:11 -0700 From: "Raj, Ashok" <ashok.raj@...el.com> To: Alex Williamson <alex.williamson@...hat.com> Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org, iommu@...ts.linux-foundation.org, Joerg Roedel <joro@...tes.org>, Bjorn Helgaas <helgaas@...nel.org>, Gage Eads <gage.eads@...el.com>, Ashok Raj <ashok.raj@...el.com> Subject: Re: [PATCH] vfio/pci: Some buggy virtual functions incorrectly report 1 for intx. On Thu, Aug 09, 2018 at 01:44:17PM -0600, Alex Williamson wrote: > On Thu, 9 Aug 2018 12:37:06 -0700 > Ashok Raj <ashok.raj@...el.com> wrote: > > > PCI_INTERRUPT_PIN should always read 0 for SRIOV Virtual Functions. > > > > Some SRIOV devices have some bugs in RTL and VF's end up reading 1 > > instead of 0 for the PIN. > > Hi Ashok, > > One question, can we identify which VFs are known to have this issue so > that users (and downstreams) can know how to prioritize this patch? > Thanks, Hi Alex, The hardware isn't public yet, so can't talk about it :-(. Once this patch gets merged, will let the OSV engagement folks drive it for inclusions. We could mark this for stable, but i would rather wait until we know the timeline when they are expecting it to be in. It shouldn't break anything since we are just enforcing the spec. Cheers, Ashok
Powered by blists - more mailing lists