Re: [PATCH 05/12] PCI: Require CAP_COMPROMISE_KERNEL for PCI BAR access

2013-03-28 Thread Josh Boyer
On Wed, Mar 27, 2013 at 11:08 AM, Kyle McMartin kmcma...@redhat.com wrote: On Wed, Mar 27, 2013 at 11:03:26AM -0400, Josh Boyer wrote: On Mon, Mar 18, 2013 at 5:32 PM, Matthew Garrett matthew.garr...@nebula.com wrote: Any hardware that can potentially generate DMA has to be locked down from

Re: [PATCH 05/12] PCI: Require CAP_COMPROMISE_KERNEL for PCI BAR access

2013-03-27 Thread Josh Boyer
On Mon, Mar 18, 2013 at 5:32 PM, Matthew Garrett matthew.garr...@nebula.com wrote: Any hardware that can potentially generate DMA has to be locked down from userspace in order to avoid it being possible for an attacker to cause arbitrary kernel behaviour. Default to paranoid - in future we can

[PATCH 05/12] PCI: Require CAP_COMPROMISE_KERNEL for PCI BAR access

2013-03-18 Thread Matthew Garrett
Any hardware that can potentially generate DMA has to be locked down from userspace in order to avoid it being possible for an attacker to cause arbitrary kernel behaviour. Default to paranoid - in future we can potentially relax this for sufficiently IOMMU-isolated devices. Signed-off-by: