From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Tosatti Subject: Re: [PATCH v3 0/2] kvm: Lock down device assignment Date: Fri, 23 Dec 2011 09:03:11 -0200 Message-ID: <20111223110311.GC24308@amt.cnet> References: <20111221045636.5773.11289.stgit@bling.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: avi@redhat.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, jan.kiszka@siemens.com, levinsasha928@gmail.com To: Alex Williamson Return-path: Content-Disposition: inline In-Reply-To: <20111221045636.5773.11289.stgit@bling.home> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Tue, Dec 20, 2011 at 09:58:57PM -0700, Alex Williamson wrote: > v2: Update API documentation for each patch > v3: Incorporate Sasha's comments: kobject path, separate func, and CONFIG_SYSFS > > Two patches to try to better secure the device assignment ioctl. > This firt patch makes KVM_DEV_ASSIGN_ENABLE_IOMMU a mandatory > option when assigning a device. I don't believe we have any > users of this option, so I think we can skip any deprecation > period, especially since it's existence is rather dangerous. > > The second patch introduces some file permission checking that Avi > suggested. If a user has been granted read/write permission to > the PCI sysfs BAR resource files, this is a good indication that > they have access to the device. We can't call sys_faccessat > directly (not exported), but the important bits are self contained > enough to include directly. This still works with sudo and libvirt > usage, the latter already grants qemu permission to these files. > Thanks, > > Alex > > --- > > Alex Williamson (2): > kvm: Device assignment permission checks > kvm: Remove ability to assign a device without iommu support Applied, thanks.