From: Kevin Wolf <kwolf@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] dmg: fix ->open failure
Date: Mon, 11 Jan 2010 15:11:52 +0100 [thread overview]
Message-ID: <4B4B31A8.6010405@redhat.com> (raw)
In-Reply-To: <20100111140000.GA28467@lst.de>
Am 11.01.2010 15:00, schrieb Christoph Hellwig:
> On Mon, Jan 11, 2010 at 02:56:16PM +0100, Kevin Wolf wrote:
>> Are you going to propose a cleaner patch? I have currently some other
>> bugs to do first, but I was certainly planning to do so. However, I'll
>> happily leave it to you if you have the time right now.
>
> I'm looking into doing it in the generic block layer, yes.
More or less the same hack, just in cleaner? Or trying to fundamentally
change things? I think you haven't answered yet to what I said in the
thread of my original hack. I'm quoting it here for convenience:
> Ok, if you start talking about layering, we can have a fundamental
> discussion on this topic and why the layering is broken anyway.
> Logically, we have image formats like qcow2, VMDK and raw, and they are
> stored in files, on CD-ROMs or general block devices. From a layering
> perspective, it is wrong to include the latter in the raw format driver
> in the first place.
Actually, I think the differentiation between raw files and host_* is at
the same level as protocols are. Probably they should be implemented
very similarly.
Do you think it's possible/worth the effort to try putting things
straight here?
Kevin
next prev parent reply other threads:[~2010-01-11 14:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 13:06 [Qemu-devel] [PATCH] dmg: fix ->open failure Christoph Hellwig
2010-01-11 13:43 ` Kevin Wolf
2010-01-11 13:46 ` Christoph Hellwig
2010-01-11 13:56 ` Kevin Wolf
2010-01-11 14:00 ` Christoph Hellwig
2010-01-11 14:11 ` Kevin Wolf [this message]
2010-01-11 17:47 ` Christoph Hellwig
2010-01-12 9:25 ` Kevin Wolf
2010-01-11 19:07 ` malc
2010-01-11 19:51 ` Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B4B31A8.6010405@redhat.com \
--to=kwolf@redhat.com \
--cc=hch@lst.de \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).