From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
bluewindow@h3c.com, nick@bytemark.co.uk
Subject: [Qemu-devel] [PATCH 0/3] nbd: fix issues when connection breaks
Date: Tue, 25 Feb 2014 11:09:55 +0100 [thread overview]
Message-ID: <1393322998-10289-1-git-send-email-stefanha@redhat.com> (raw)
The first patch ensures the nbd_receive_reply() fd handler is unregistered when
the connection to the server breaks. This avoids high CPU consumption and
flooding error messages.
The second patch introduces an NBD server fault injection script. Using this
fake NBD server it is possible to exercise error handling code paths in the NBD
client.
The third patch adds qemu-iotests test case 080 to verify qemu-io exits with an
error at each point where the connection can break.
Stefan Hajnoczi (3):
nbd: close socket if connection breaks
tests: add nbd-fault-injector.py utility
qemu-iotests: add 080 NBD client disconnect tests
block/nbd-client.c | 33 +++--
tests/qemu-iotests/080 | 91 ++++++++++++
tests/qemu-iotests/080.out | 73 ++++++++++
tests/qemu-iotests/group | 1 +
tests/qemu-iotests/nbd-fault-injector.py | 231 +++++++++++++++++++++++++++++++
5 files changed, 414 insertions(+), 15 deletions(-)
create mode 100755 tests/qemu-iotests/080
create mode 100644 tests/qemu-iotests/080.out
create mode 100755 tests/qemu-iotests/nbd-fault-injector.py
--
1.8.5.3
next reply other threads:[~2014-02-25 10:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 10:09 Stefan Hajnoczi [this message]
2014-02-25 10:09 ` [Qemu-devel] [PATCH 1/3] nbd: close socket if connection breaks Stefan Hajnoczi
2014-02-25 10:09 ` [Qemu-devel] [PATCH 2/3] tests: add nbd-fault-injector.py utility Stefan Hajnoczi
2014-02-25 11:45 ` Nick Thomas
2014-02-25 16:25 ` Stefan Hajnoczi
2014-02-25 10:09 ` [Qemu-devel] [PATCH 3/3] qemu-iotests: add 080 NBD client disconnect tests Stefan Hajnoczi
2014-02-25 10:16 ` Kevin Wolf
2014-02-25 11:16 ` Stefan Hajnoczi
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=1393322998-10289-1-git-send-email-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=bluewindow@h3c.com \
--cc=kwolf@redhat.com \
--cc=nick@bytemark.co.uk \
--cc=pbonzini@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).