From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NHb4M-0001kr-Dn for qemu-devel@nongnu.org; Mon, 07 Dec 2009 05:43:54 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NHb4H-0001iV-AT for qemu-devel@nongnu.org; Mon, 07 Dec 2009 05:43:53 -0500 Received: from [199.232.76.173] (port=48581 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NHb4G-0001iP-Qp for qemu-devel@nongnu.org; Mon, 07 Dec 2009 05:43:48 -0500 Received: from mx1.redhat.com ([209.132.183.28]:1749) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NHb4G-0006f0-AU for qemu-devel@nongnu.org; Mon, 07 Dec 2009 05:43:48 -0500 Message-ID: <4B1CDC1F.9000705@redhat.com> Date: Mon, 07 Dec 2009 11:42:39 +0100 From: Kevin Wolf MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] Disk image shared and exclusive locks. References: <20091204165301.GA4167@amd.home.annexia.org> <4B1943A0.7030509@codemonkey.ws> <20091204215517.GA5938@amd.home.annexia.org> <4B198D5B.5080803@codemonkey.ws> <4B1A98D9.7010408@redhat.com> <4B1A9C9F.5040705@codemonkey.ws> <4B1A9E83.2050103@redhat.com> <4B1A9F8C.3010106@codemonkey.ws> <20091207103128.GA26970@shareable.org> In-Reply-To: <20091207103128.GA26970@shareable.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jamie Lokier Cc: "Richard W.M. Jones" , qemu-devel@nongnu.org, Avi Kivity Am 07.12.2009 11:31, schrieb Jamie Lokier: > So the distinction read/write makes more sense. Can anyone think of a > situation where a shared lock on an image opened for writing is useful? I think there are people using shared writable images with cluster file systems. Kevin