| 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: Wed, 23 Nov 2011 11:56:12 +0100 From: Joerg Roedel <joerg.roedel@....com> To: Chris Wright <chrisw@...s-sol.org> CC: Joerg Roedel <joro@...tes.org>, <linux-pci@...r.kernel.org>, <dwmw2@...radead.org>, <iommu@...ts.linux-foundation.org>, <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] iommu: Include MSI susceptibility to DMA in creating iommu groups On Mon, Nov 21, 2011 at 03:35:05PM -0800, Chris Wright wrote: > What is the value of a group w/out complete isolation? There is still isolation for DMA. This may be sufficient for non-KVM use-cases like a device driver partially implemented in userspace. There is no no guest then that can attack the host with wrong interrupts. > Is there a practical problem w/ conflating the subtleties above? Same argument as above. It ties the the iommu_group interface to the KVM use case. Another more pratical impact of this patch is that a reboot is required to re-enable iommu-groups. When the check happens in VFIO it is a simple module-reload. Joerg -- AMD Operating System Research Center Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach General Managers: Alberto Bozzo, Andrew Bowd Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632 -- 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