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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 10 Aug 2021 08:49:37 +0100 From: Marc Zyngier <maz@...nel.org> To: Thomas Gleixner <tglx@...utronix.de> Cc: LKML <linux-kernel@...r.kernel.org>, Alex Williamson <alex.williamson@...hat.com>, "Raj, Ashok" <ashok.raj@...el.com>, "David S. Miller" <davem@...emloft.net>, Bjorn Helgaas <bhelgaas@...gle.com>, linux-pci@...r.kernel.org, Kevin Tian <kevin.tian@...el.com>, Ingo Molnar <mingo@...nel.org>, x86@...nel.org, linux-s390@...r.kernel.org, Niklas Schnelle <schnelle@...ux.ibm.com>, Gerald Schaefer <gerald.schaefer@...ux.ibm.com>, Heiko Carstens <hca@...ux.ibm.com>, Christian Borntraeger <borntraeger@...ibm.com> Subject: Re: [patch V2 00/19] PCI/MSI, x86: Cure a couple of inconsistencies On 2021-07-29 22:51, Thomas Gleixner wrote: > A recent discussion about the PCI/MSI management for virtio unearthed a > violation of the MSI-X specification vs. writing the MSI-X message: > under > certain circumstances the entry is written without being masked. > > While looking at that and the related violation of the x86 non-remapped > interrupt affinity mechanism a few other issues were discovered by > inspection. > > The following series addresses these. > > Note this does not fix the virtio issue, but while staring at the above > problems I came up with a plan to address this. I'm still trying to > convince myself that I can get away without sprinkling locking all over > the > place, so don't hold your breath that this will materialize tomorrow. For the patches I haven't acked yet, and with the fix on patch 18: Reviewed-by: Marc Zyngier <maz@...nel.org> Tested-by: Marc Zyngier <maz@...nel.org> Thanks, M.
Powered by blists - more mailing lists