From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH for-3.1? 0/2] NBD dirty bitmap cleanups
Date: Thu, 29 Nov 2018 19:11:44 -0600 [thread overview]
Message-ID: <20181130011146.3065277-1-eblake@redhat.com> (raw)
I'm working on a bigger series to add 'qemu-nbd --list' that shows
all details about all exports of a given server. In the process,
it turned up a couple of bugs. By themselves, these are not enough
to cause -rc4 (the bugs already existed in 3.0; this is not a
regression fix), but if we have -rc4 for any other reason, both
of these would be nice to have as it makes incremental backups
easier to manage.
Eric Blake (2):
nbd/server: Advertise all contexts in response to bare LIST
nbd/client: Make x-dirty-bitmap more reliable
nbd/client.c | 21 +++++++++++++++++++++
nbd/server.c | 1 +
2 files changed, 22 insertions(+)
--
2.17.2
next reply other threads:[~2018-11-30 1:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 1:11 Eric Blake [this message]
2018-11-30 1:41 ` [Qemu-devel] [PATCH for-3.1? 0/2] NBD dirty bitmap cleanups Eric Blake
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=20181130011146.3065277-1-eblake@redhat.com \
--to=eblake@redhat.com \
--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).