From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL v2 00/17] NBD patches for 2018-03-13 (2.12 softfreeze)
Date: Tue, 13 Mar 2018 15:50:06 -0500 [thread overview]
Message-ID: <20180313205023.711304-1-eblake@redhat.com> (raw)
The following changes since commit 026aaf47c02b79036feb830206cfebb2a726510d:
Merge remote-tracking branch 'remotes/ehabkost/tags/python-next-pull-request' into staging (2018-03-13 16:26:44 +0000)
are available in the Git repository at:
git://repo.or.cz/qemu/ericb.git tags/pull-nbd-2018-03-13-v2
for you to fetch changes up to 65374c1aa6263a4e2b566d15a9fd9b2105954a1b:
iotests: new test 209 for NBD BLOCK_STATUS (2018-03-13 15:44:09 -0500)
In v2: fix uninitialized variable warning [patchew]
(only mailing patches that changed since v1)
----------------------------------------------------------------
nbd patches for 2018-03-13
- Eric Blake: iotests: Fix stuck NBD process on 33
- Vladimir Sementsov-Ogievskiy: 0/5 nbd server fixing and refactoring before BLOCK_STATUS
- Eric Blake: nbd/server: Honor FUA request on NBD_CMD_TRIM
- Stefan Hajnoczi: 0/2 block: fix nbd-server-stop crash after blockdev-snapshot-sync
- Vladimir Sementsov-Ogievskiy: nbd block status base:allocation
----------------------------------------------------------------
Eric Blake (2):
iotests: Fix stuck NBD process on 33
nbd/server: Honor FUA request on NBD_CMD_TRIM
Stefan Hajnoczi (2):
block: let blk_add/remove_aio_context_notifier() tolerate BDS changes
iotests: add 208 nbd-server + blockdev-snapshot-sync test case
Vladimir Sementsov-Ogievskiy (13):
nbd/server: move nbd_co_send_structured_error up
nbd/server: fix sparse read
nbd/server: fix: check client->closing before sending reply
nbd/server: refactor nbd_trip: cmd_read and generic reply
nbd/server: refactor nbd_trip: split out nbd_handle_request
nbd/server: add nbd_opt_invalid helper
nbd/server: add nbd_read_opt_name helper
nbd: BLOCK_STATUS for standard get_block_status function: server part
block/nbd-client: save first fatal error in nbd_iter_error
nbd: BLOCK_STATUS for standard get_block_status function: client part
iotests.py: tiny refactor: move system imports up
iotests: add file_path helper
iotests: new test 209 for NBD BLOCK_STATUS
block/nbd-client.h | 6 +
include/block/nbd.h | 3 +
block/block-backend.c | 63 ++++
block/nbd-client.c | 154 ++++++++-
block/nbd.c | 3 +
nbd/client.c | 117 +++++++
nbd/server.c | 725 ++++++++++++++++++++++++++++++++----------
block/trace-events | 2 +
tests/qemu-iotests/033 | 1 +
tests/qemu-iotests/208 | 55 ++++
tests/qemu-iotests/208.out | 9 +
tests/qemu-iotests/209 | 34 ++
tests/qemu-iotests/209.out | 2 +
tests/qemu-iotests/group | 2 +
tests/qemu-iotests/iotests.py | 37 ++-
15 files changed, 1047 insertions(+), 166 deletions(-)
create mode 100755 tests/qemu-iotests/208
create mode 100644 tests/qemu-iotests/208.out
create mode 100755 tests/qemu-iotests/209
create mode 100644 tests/qemu-iotests/209.out
--
2.14.3
next reply other threads:[~2018-03-13 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 20:50 Eric Blake [this message]
2018-03-13 20:50 ` [Qemu-devel] [PULL v2 14/17] nbd: BLOCK_STATUS for standard get_block_status function: client part Eric Blake
2018-03-16 14:15 ` [Qemu-devel] [PULL v2 00/17] NBD patches for 2018-03-13 (2.12 softfreeze) 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=20180313205023.711304-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).