From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Subject: [PULL v2 00/20] NBD patches for 2021-02-02
Date: Wed, 3 Feb 2021 08:24:16 -0600 [thread overview]
Message-ID: <20210203142436.703098-1-eblake@redhat.com> (raw)
The following changes since commit 8360ebeb4f4a707984cafd1a22c049ec82ddcb4c:
Merge remote-tracking branch 'remotes/ehabkost-gl/tags/machine-next-pull-request' into staging (2021-02-03 09:54:21 +0000)
are available in the Git repository at:
https://repo.or.cz/qemu/ericb.git tags/pull-nbd-2021-02-02-v2
for you to fetch changes up to 5082fc82a6bc3fc06a04be47d39777c7cff61e5b:
nbd: make nbd_read* return -EIO on error (2021-02-03 08:17:12 -0600)
v2: fix accidental inclusion of .rej file from merge resolution
[only affected patches re-sent]
----------------------------------------------------------------
nbd patches for 2021-02-02
- more cleanup from iotest python conversion
- progress towards consistent use of signed 64-bit types through block layer
- fix some crashes related to NBD reconnect
----------------------------------------------------------------
Eric Blake (2):
iotests: Fix expected whitespace for 185
block: use int64_t as bytes type in tracked requests
Roman Kagan (3):
block/nbd: only detach existing iochannel from aio_context
block/nbd: only enter connection coroutine if it's present
nbd: make nbd_read* return -EIO on error
Vladimir Sementsov-Ogievskiy (15):
block: refactor bdrv_check_request: add errp
util/iov: make qemu_iovec_init_extended() honest
block: fix theoretical overflow in bdrv_init_padding()
block/io: refactor bdrv_pad_request(): move bdrv_pad_request() up
block/io: bdrv_pad_request(): support qemu_iovec_init_extended failure
block/throttle-groups: throttle_group_co_io_limits_intercept(): 64bit bytes
block/io: improve bdrv_check_request: check qiov too
block/io: use int64_t bytes in driver wrappers
block/io: support int64_t bytes in bdrv_co_do_pwrite_zeroes()
block/io: support int64_t bytes in bdrv_aligned_pwritev()
block/io: support int64_t bytes in bdrv_co_do_copy_on_readv()
block/io: support int64_t bytes in bdrv_aligned_preadv()
block/io: support int64_t bytes in bdrv_co_p{read,write}v_part()
block/io: support int64_t bytes in read/write wrappers
block/io: use int64_t bytes in copy_range
include/block/block.h | 17 +--
include/block/block_int.h | 26 ++--
include/block/nbd.h | 7 +-
include/block/throttle-groups.h | 2 +-
include/qemu/iov.h | 2 +-
block/io.c | 274 ++++++++++++++++++++++++++++------------
block/blkverify.c | 2 +-
block/file-posix.c | 2 +-
block/nbd.c | 25 ++--
block/throttle-groups.c | 5 +-
tests/test-write-threshold.c | 5 +-
util/iov.c | 25 +++-
block/trace-events | 12 +-
tests/qemu-iotests/185.out | 2 +-
tests/qemu-iotests/206.out | 2 +-
15 files changed, 275 insertions(+), 133 deletions(-)
--
2.30.0
next reply other threads:[~2021-02-03 14:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 14:24 Eric Blake [this message]
2021-02-03 14:24 ` [PULL v2 05/20] block/io: refactor bdrv_pad_request(): move bdrv_pad_request() up Eric Blake
2021-02-03 14:24 ` [PULL v2 09/20] block: use int64_t as bytes type in tracked requests Eric Blake
2021-02-03 14:24 ` [PULL v2 12/20] block/io: support int64_t bytes in bdrv_aligned_pwritev() Eric Blake
2021-02-03 19:35 ` [PULL v2 00/20] NBD patches for 2021-02-02 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=20210203142436.703098-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).