From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-block@nongnu.org, Eric Blake <eblake@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/3] nbd-client: enter read_reply_co during init to avoid crash
Date: Tue, 29 Aug 2017 13:27:42 +0100 [thread overview]
Message-ID: <20170829122745.14309-1-stefanha@redhat.com> (raw)
v2:
* Rewrote Patch 1 following Paolo's suggestion [Paolo]
See Patch 1 for the segfault fix. Patches 2 & 3 add qemu-iotests coverage.
This is a rare crash that we'll probably only see in testing. It only seems to
happen with UNIX domain sockets.
Stefan Hajnoczi (3):
nbd-client: avoid read_reply_co entry if send failed
qemu-iotests: improve nbd-fault-injector.py startup protocol
qemu-iotests: test NBD over UNIX domain sockets in 083
block/nbd-client.c | 25 ++----
tests/qemu-iotests/083 | 138 ++++++++++++++++++-----------
tests/qemu-iotests/083.out | 145 +++++++++++++++++++++++++++----
tests/qemu-iotests/common.filter | 4 +-
tests/qemu-iotests/nbd-fault-injector.py | 4 +
5 files changed, 228 insertions(+), 88 deletions(-)
--
2.13.5
next reply other threads:[~2017-08-29 12:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 12:27 Stefan Hajnoczi [this message]
2017-08-29 12:27 ` [Qemu-devel] [PATCH v2 1/3] nbd-client: avoid read_reply_co entry if send failed Stefan Hajnoczi
2017-08-29 19:13 ` Eric Blake
2017-09-26 18:12 ` Eric Blake
2017-08-29 12:27 ` [Qemu-devel] [PATCH v2 2/3] qemu-iotests: improve nbd-fault-injector.py startup protocol Stefan Hajnoczi
2017-08-29 12:27 ` [Qemu-devel] [PATCH v2 3/3] qemu-iotests: test NBD over UNIX domain sockets in 083 Stefan Hajnoczi
2017-08-29 21:58 ` [Qemu-devel] [PATCH v2 0/3] nbd-client: enter read_reply_co during init to avoid crash 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=20170829122745.14309-1-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/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).