linux-kernel - Re: [PATCH] uio_pci_generic does not export memory resources

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 08 Jun 2012 08:16:49 -0600
From:	Alex Williamson <alex.williamson@...hat.com>
To:	Jan Kiszka <jan.kiszka@...mens.com>
Cc:	"Michael S. Tsirkin" <mst@...hat.com>,
	Dominic Eschweiler <eschweiler@...s.uni-frankfurt.de>,
	"Hans J. Koch" <hjk@...sjkoch.de>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] uio_pci_generic does not export memory resources

On Fri, 2012-06-08 at 15:16 +0200, Jan Kiszka wrote:
> On 2012-06-08 15:03, Michael S. Tsirkin wrote:
> >> +    /* set master */
> >> +	pci_set_master(pdev);
> >> +
> >> +    /* set DMA mask */
> >> +	err = pci_set_dma_mask(pdev, DMA_BIT_MASK(64));
> > 
> > uio currently only supports devices which do not
> > do DMA.
> > 
> > DMA from uio controlled devices is a no no unless
> > it's behind an IOMMU which can protect us from
> > random memory corruptions this could cause.
> > 
> > In the later case it's OK but we need some code
> > to check this and program the IOMMU appropriately.
> 
> AKA: VFIO. :)
> 
> Dominic, maybe you want to have a look at Alex's work:
> https://github.com/awilliam/linux-vfio

Yes, thanks Jan.  This is exactly what VFIO does.  VFIO provides secure
config space access, resource access, DMA mapping services, and full
interrupt support to userspace.  I'm currently working to get this
upstream, probably targeting 3.6 at this point, and would love to have
more users to help make that happen.  Please take a look at the vfio-3.4
branch in the tree above.  See this tree for Qemu's usage of VFIO for
device assignment:
https://github.com/awilliam/qemu-vfio (vfio-ng)

Look forward to your feedback.  Thanks,

Alex

--
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/