From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Subject: [PULL v2 0/5] NBD patches for 2019-09-24
Date: Wed, 25 Sep 2019 08:37:35 -0500 [thread overview]
Message-ID: <20190925133740.30401-1-eblake@redhat.com> (raw)
The following changes since commit 2f93a3ecdd3bb060bd04f698ccafe66efd98563a:
Merge remote-tracking branch 'remotes/davidhildenbrand/tags/s390x-tcg-2019-09-23' into staging (2019-09-23 15:44:52 +0100)
are available in the Git repository at:
https://repo.or.cz/qemu/ericb.git tags/pull-nbd-2019-09-24-v2
for you to fetch changes up to da5e1169183ca6eb6fb470dc32ed1bfc24d1d406:
util/qemu-sockets: fix keep_alive handling in inet_connect_saddr (2019-09-25 08:15:44 -0500)
For v2 - add one more patch
----------------------------------------------------------------
nbd patches for 2019-09-24
- Improved error message for plaintext client of encrypted server
- Fix various assertions when -object iothread is in use
- Silence a Coverity error for use-after-free on error path
----------------------------------------------------------------
Eric Blake (3):
nbd/client: Add hint when TLS is missing
nbd: Grab aio context lock in more places
tests: Use iothreads during iotest 223
Sergio Lopez (1):
nbd/server: attach client channel to the export's AioContext
Vladimir Sementsov-Ogievskiy (1):
util/qemu-sockets: fix keep_alive handling in inet_connect_saddr
include/block/nbd.h | 1 +
blockdev-nbd.c | 14 ++++++++++++--
nbd/client.c | 1 +
nbd/server.c | 27 +++++++++++++++++++++++----
util/qemu-sockets.c | 5 +++--
tests/qemu-iotests/223 | 6 ++++--
tests/qemu-iotests/223.out | 1 +
tests/qemu-iotests/233.out | 2 ++
8 files changed, 47 insertions(+), 10 deletions(-)
--
2.21.0
next reply other threads:[~2019-09-25 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 13:37 Eric Blake [this message]
2019-09-25 13:37 ` [PULL v2 5/5] util/qemu-sockets: fix keep_alive handling in inet_connect_saddr Eric Blake
2019-09-26 12:56 ` [PULL v2 0/5] NBD patches for 2019-09-24 Peter Maydell
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=20190925133740.30401-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).