From: Stefan Hajnoczi <stefanha@gmail.com>
To: Bug 1362635 <1362635@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1362635] Re: bdrv_read co-routine re-entered recursively
Date: Mon, 8 Sep 2014 10:54:00 +0100 [thread overview]
Message-ID: <20140908095400.GH7638@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20140908080119.442.60110.malone@gac.canonical.com>
[-- Attachment #1: Type: text/plain, Size: 298 bytes --]
On Mon, Sep 08, 2014 at 08:01:18AM -0000, senya wrote:
> Thanks.. I know about Fam's patch, but I need reverse delta backups, and
> Jagane's work is more appropriate then qemu snapshot approach.
Jagane's approach needs a lot of work to make it mergable, that's why I
suggested Fam's work.
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-09-08 9:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 14:19 [Qemu-devel] [Bug 1362635] [NEW] bdrv_read co-routine re-entered recursively senya
2014-08-29 11:16 ` [Qemu-devel] [Bug 1362635] " senya
2014-08-29 15:54 ` Stefan Hajnoczi
2014-09-01 7:55 ` senya
2014-09-01 15:44 ` Stefan Hajnoczi
2014-09-01 13:38 ` senya
2014-09-08 8:01 ` senya
2014-09-08 9:54 ` Stefan Hajnoczi [this message]
2018-04-13 21:41 ` Thomas Huth
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=20140908095400.GH7638@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=1362635@bugs.launchpad.net \
--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).