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
| ||
|
Message-ID: <20151006223202.66ab0b87@samsung9> Date: Tue, 6 Oct 2015 22:32:02 +0100 From: Stephen Hemminger <stephen@...workplumber.org> To: Alex Williamson <alex.williamson@...hat.com> Cc: Avi Kivity <avi@...lladb.com>, "Michael S. Tsirkin" <mst@...hat.com>, Vlad Zolotarov <vladz@...udius-systems.com>, Greg KH <gregkh@...uxfoundation.org>, linux-kernel@...r.kernel.org, hjk@...sjkoch.de, corbet@....net, bruce.richardson@...el.com, avi@...udius-systems.com, gleb@...udius-systems.com, alexander.duyck@...il.com Subject: Re: [PATCH v3 2/3] uio_pci_generic: add MSI/MSI-X support On Tue, 06 Oct 2015 12:51:20 -0600 Alex Williamson <alex.williamson@...hat.com> wrote: > Of course this is entirely unsafe and this no-iommu driver should taint > the kernel, but it at least standardizes on one userspace API and you're > already doing completely unsafe things with uio. vfio should be > enlightened at least to the point that it allows only privileged users > access to devices under such a (lack of) iommu I agree with the design, but not with the taint argument. (Unless you want to taint any and all use of UIO drivers which can already do this). -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists