From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:41735) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qliyj-0005hE-LR for qemu-devel@nongnu.org; Tue, 26 Jul 2011 10:51:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qliyi-0008GQ-Bw for qemu-devel@nongnu.org; Tue, 26 Jul 2011 10:51:25 -0400 Received: from mx1.redhat.com ([209.132.183.28]:36388) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qliyi-0008GH-4t for qemu-devel@nongnu.org; Tue, 26 Jul 2011 10:51:24 -0400 Message-ID: <4E2ED512.1040007@redhat.com> Date: Tue, 26 Jul 2011 16:54:10 +0200 From: Kevin Wolf MIME-Version: 1.0 References: <1311684710-27074-1-git-send-email-coreyb@linux.vnet.ibm.com> <20110726130211.GA2853@lst.de> <4E2EC9B6.8060105@redhat.com> <4E2ED33F.8090305@us.ibm.com> In-Reply-To: <4E2ED33F.8090305@us.ibm.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v3] Add support for fd: protocol List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Corey Bryant Cc: aliguori@us.ibm.com, libvir-list@redhat.com, Corey Bryant , qemu-devel@nongnu.org, tchicks@us.ibm.com, Christoph Hellwig Am 26.07.2011 16:46, schrieb Corey Bryant: > > On 07/26/2011 10:05 AM, Kevin Wolf wrote: >> Am 26.07.2011 15:02, schrieb Christoph Hellwig: >>>> I have to say I really hate it. We've been working hard on getting rid >>>> of special cases in the qemu block layer, and this sprinkles them all >>>> over. I'd recommend to fix your security model instead. >> I think the problem here is more with the implementation that with the >> intention. >> >> I agree that you just can't do this. A patch adding support for a fd: >> protocol should touch block/fd.c and nothing else. You can add some >> supporting patches that extend the generic block layer to support e.g. >> formats that can't reopen. However, if you touch the code of other block >> drivers, you're doing it wrong. > > I'll look into this approach, but on the surface it seems like this > could prevent a lot of code reuse in block/raw-posix.c. What I meant here is more about modifying qcow2, VMDK etc. I still need to look into the details of what you share with raw-posix.c. Kevin