From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: xl create should refuse to share block devices RW between domains Date: Tue, 27 Jul 2010 08:18:50 -0700 Message-ID: <4C4EF8DA.70903@goop.org> References: <4C4E2A06.9070604@goop.org> <1280218738.5872.8148.camel@zakaz.uk.xensource.com> <1280228106.5872.8479.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1280228106.5872.8479.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: Xen-devel@lists.xensource.com, Ian Jackson , Daniel Stodden , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On 07/27/2010 03:55 AM, Ian Campbell wrote: >> I also think that tap_ctl_create is the right place to do these checks, >> not a script called by udev after the device has been created. > Agreed. tapdisk should be taking out a flock() or something similar on > any vhd files it is going to write to and should fail if it can't lock > the file. I'm not sure that would work for physical device/lvm backing. J