From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Subject: [PULL v2 0/8] NBD patches through 2020-10-08
Date: Fri, 9 Oct 2020 08:54:21 -0500 [thread overview]
Message-ID: <20201009135429.1122744-1-eblake@redhat.com> (raw)
The following changes since commit 497d415d76b9f59fcae27f22df1ca2c3fa4df64e:
Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20201008-1' into staging (2020-10-08 21:41:20 +0100)
are available in the Git repository at:
https://repo.or.cz/qemu/ericb.git tags/pull-nbd-2020-10-08-v2
for you to fetch changes up to 351a587410eff515ee28da619867030217b62457:
nbd: Simplify meta-context parsing (2020-10-09 08:34:15 -0500)
v2: fix BSD compilation error
----------------------------------------------------------------
nbd patches for 2020-10-08
- silence compilation warnings
- more fixes to prevent reconnect hangs
- improve 'qemu-nbd' termination behavior
- cleaner NBD protocol compliance on string handling
----------------------------------------------------------------
Christian Borntraeger (1):
nbd: silence maybe-uninitialized warnings
Eric Blake (3):
qemu-nbd: Honor SIGINT and SIGHUP
nbd/server: Reject embedded NUL in NBD strings
nbd: Simplify meta-context parsing
Vladimir Sementsov-Ogievskiy (4):
block/nbd: fix drain dead-lock because of nbd reconnect-delay
block/nbd: correctly use qio_channel_detach_aio_context when needed
block/nbd: fix reconnect-delay
block/nbd: nbd_co_reconnect_loop(): don't connect if drained
block/nbd.c | 71 ++++++++++++++++---
nbd/server.c | 221 ++++++++++++++++++++++++-----------------------------------
qemu-nbd.c | 15 ++--
3 files changed, 157 insertions(+), 150 deletions(-)
--
2.28.0
next reply other threads:[~2020-10-09 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 13:54 Eric Blake [this message]
2020-10-09 13:54 ` [PULL v2 6/8] qemu-nbd: Honor SIGINT and SIGHUP Eric Blake
2020-10-09 18:50 ` [PULL v2 0/8] NBD patches through 2020-10-08 Peter Maydell
2020-10-09 19:52 ` 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=20201009135429.1122744-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).