From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: [PULL 0/9] Block patches for 6.0-rc1
Date: Tue, 30 Mar 2021 14:39:48 +0200 [thread overview]
Message-ID: <20210330123957.826170-1-mreitz@redhat.com> (raw)
The following changes since commit ec2e6e016d24bd429792d08cf607e4c5350dcdaa:
Merge remote-tracking branch 'remotes/vivier2/tags/linux-user-for-6.0-pull-request' into staging (2021-03-28 19:49:57 +0100)
are available in the Git repository at:
https://github.com/XanClic/qemu.git tags/pull-block-2021-03-30
for you to fetch changes up to 2ec7e8a94668efccf7f45634584cfa19a83fc553:
iotests/244: Test preallocation for data-file-raw (2021-03-30 13:02:11 +0200)
----------------------------------------------------------------
Block patches for 6.0-rc1:
- Mark the qcow2 cache clean timer as external to fix record/replay
- Fix the mirror filter node's permissions so that an external process
cannot grab an image while it is used as the mirror source
- Add documentation about FUSE exports to the storage daemon
- When creating a qcow2 image with the data-file-raw option, all
metadata structures should be preallocated
- iotest fixes
----------------------------------------------------------------
Connor Kuehl (1):
iotests: fix 051.out expected output after error text touchups
Max Reitz (6):
iotests/116: Fix reference output
iotests/046: Filter request length
block/mirror: Fix mirror_top's permissions
qsd: Document FUSE exports
qcow2: Force preallocation with data-file-raw
iotests/244: Test preallocation for data-file-raw
Pavel Dovgalyuk (1):
qcow2: use external virtual timers
Tao Xu (1):
iotests: Fix typo in iotest 051
docs/tools/qemu-storage-daemon.rst | 19 +++++
block/mirror.c | 32 +++++++--
block/qcow2.c | 41 ++++++++++-
storage-daemon/qemu-storage-daemon.c | 4 ++
tests/qemu-iotests/046 | 3 +-
tests/qemu-iotests/046.out | 104 +++++++++++++--------------
tests/qemu-iotests/051 | 2 +-
tests/qemu-iotests/051.out | 6 +-
tests/qemu-iotests/051.pc.out | 4 +-
tests/qemu-iotests/116.out | 12 ++--
tests/qemu-iotests/244 | 104 +++++++++++++++++++++++++++
tests/qemu-iotests/244.out | 68 ++++++++++++++++--
12 files changed, 319 insertions(+), 80 deletions(-)
--
2.29.2
next reply other threads:[~2021-03-30 12:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 12:39 Max Reitz [this message]
2021-03-30 12:39 ` [PULL 1/9] iotests: Fix typo in iotest 051 Max Reitz
2021-03-30 12:39 ` [PULL 2/9] iotests: fix 051.out expected output after error text touchups Max Reitz
2021-03-30 12:39 ` [PULL 3/9] iotests/116: Fix reference output Max Reitz
2021-03-30 12:39 ` [PULL 4/9] qcow2: use external virtual timers Max Reitz
2021-03-30 12:39 ` [PULL 5/9] iotests/046: Filter request length Max Reitz
2021-03-30 12:39 ` [PULL 6/9] block/mirror: Fix mirror_top's permissions Max Reitz
2021-03-30 12:39 ` [PULL 7/9] qsd: Document FUSE exports Max Reitz
2021-03-30 12:39 ` [PULL 8/9] qcow2: Force preallocation with data-file-raw Max Reitz
2021-03-30 12:39 ` [PULL 9/9] iotests/244: Test preallocation for data-file-raw Max Reitz
2021-03-30 15:34 ` [PULL 0/9] Block patches for 6.0-rc1 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=20210330123957.826170-1-mreitz@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.