From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: [PULL 00/20] Block layer patches
Date: Wed, 2 Jun 2021 15:45:09 +0200 [thread overview]
Message-ID: <20210602134529.231756-1-kwolf@redhat.com> (raw)
The following changes since commit dd2db39d78431ab5a0b78777afaab3d61e94533e:
Merge remote-tracking branch 'remotes/ehabkost-gl/tags/x86-next-pull-request' into staging (2021-06-01 21:23:26 +0100)
are available in the Git repository at:
git://repo.or.cz/qemu/kevin.git tags/for-upstream
for you to fetch changes up to b317006a3f1f04191a7981cef83417cb2477213b:
docs/secure-coding-practices: Describe how to use 'null-co' block driver (2021-06-02 14:29:14 +0200)
----------------------------------------------------------------
Block layer patches
- NBD server: Fix crashes related to switching between AioContexts
- file-posix: Workaround for discard/write_zeroes on buggy filesystems
- Follow-up fixes for the reopen vs. permission changes
- quorum: Fix error handling for flush
- block-copy: Refactor copy_range handling
- docs: Describe how to use 'null-co' block driver
----------------------------------------------------------------
Lukas Straub (1):
block/quorum: Provide .bdrv_co_flush instead of .bdrv_co_flush_to_disk
Philippe Mathieu-Daudé (1):
docs/secure-coding-practices: Describe how to use 'null-co' block driver
Sergio Lopez (2):
block-backend: add drained_poll
nbd/server: Use drained block ops to quiesce the server
Thomas Huth (2):
block/file-posix: Fix problem with fallocate(PUNCH_HOLE) on GPFS
block/file-posix: Try other fallbacks after invalid FALLOC_FL_ZERO_RANGE
Vladimir Sementsov-Ogievskiy (14):
qemu-io-cmds: assert that we don't have .perm requested in no-blk case
block/vvfat: child_vvfat_qcow: add .get_parent_aio_context, fix crash
block/vvfat: fix vvfat_child_perm crash
block: consistently use bdrv_is_read_only()
block: drop BlockDriverState::read_only
block: drop BlockBackendRootState::read_only
block: document child argument of bdrv_attach_child_common()
block-backend: improve blk_root_get_parent_desc()
block: improve bdrv_child_get_parent_desc()
block/vvfat: inherit child_vvfat_qcow from child_of_bds
block: simplify bdrv_child_user_desc()
block: improve permission conflict error message
block-copy: fix block_copy_task_entry() progress update
block-copy: refactor copy_range handling
docs/devel/secure-coding-practices.rst | 9 ++++
include/block/block.h | 1 +
include/block/block_int.h | 2 -
include/sysemu/block-backend.h | 4 ++
block.c | 82 ++++++++++++++++++++--------------
block/block-backend.c | 26 +++++------
block/block-copy.c | 80 ++++++++++++++++++++++-----------
block/commit.c | 2 +-
block/file-posix.c | 29 ++++++++----
block/io.c | 4 +-
block/qapi.c | 2 +-
block/qcow2-snapshot.c | 2 +-
block/qcow2.c | 5 +--
block/quorum.c | 2 +-
block/snapshot.c | 2 +-
block/vhdx-log.c | 2 +-
block/vvfat.c | 14 +++---
blockdev.c | 3 +-
nbd/server.c | 82 +++++++++++++++++++++++++---------
qemu-io-cmds.c | 14 +++++-
tests/unit/test-block-iothread.c | 6 ---
tests/qemu-iotests/283.out | 2 +-
tests/qemu-iotests/307.out | 2 +-
tests/qemu-iotests/tests/qsd-jobs.out | 2 +-
24 files changed, 241 insertions(+), 138 deletions(-)
next reply other threads:[~2021-06-02 13:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 13:45 Kevin Wolf [this message]
2021-06-02 13:45 ` [PULL 01/20] block/quorum: Provide .bdrv_co_flush instead of .bdrv_co_flush_to_disk Kevin Wolf
2021-06-02 13:45 ` [PULL 02/20] qemu-io-cmds: assert that we don't have .perm requested in no-blk case Kevin Wolf
2021-06-02 13:45 ` [PULL 03/20] block/vvfat: child_vvfat_qcow: add .get_parent_aio_context, fix crash Kevin Wolf
2021-06-02 13:45 ` [PULL 04/20] block/vvfat: fix vvfat_child_perm crash Kevin Wolf
2021-06-02 13:45 ` [PULL 05/20] block: consistently use bdrv_is_read_only() Kevin Wolf
2021-06-02 13:45 ` [PULL 06/20] block: drop BlockDriverState::read_only Kevin Wolf
2021-06-02 13:45 ` [PULL 07/20] block: drop BlockBackendRootState::read_only Kevin Wolf
2021-06-02 13:45 ` [PULL 08/20] block/file-posix: Fix problem with fallocate(PUNCH_HOLE) on GPFS Kevin Wolf
2021-06-02 13:45 ` [PULL 09/20] block/file-posix: Try other fallbacks after invalid FALLOC_FL_ZERO_RANGE Kevin Wolf
2021-06-02 13:45 ` [PULL 10/20] block: document child argument of bdrv_attach_child_common() Kevin Wolf
2021-06-02 13:45 ` [PULL 11/20] block-backend: improve blk_root_get_parent_desc() Kevin Wolf
2021-06-02 13:45 ` [PULL 12/20] block: improve bdrv_child_get_parent_desc() Kevin Wolf
2021-06-02 13:45 ` [PULL 13/20] block/vvfat: inherit child_vvfat_qcow from child_of_bds Kevin Wolf
2021-06-02 13:45 ` [PULL 14/20] block: simplify bdrv_child_user_desc() Kevin Wolf
2021-06-02 13:45 ` [PULL 15/20] block: improve permission conflict error message Kevin Wolf
2021-06-02 13:45 ` [PULL 16/20] block-backend: add drained_poll Kevin Wolf
2021-06-02 13:45 ` [PULL 17/20] nbd/server: Use drained block ops to quiesce the server Kevin Wolf
2021-06-02 13:45 ` [PULL 18/20] block-copy: fix block_copy_task_entry() progress update Kevin Wolf
2021-06-02 13:45 ` [PULL 19/20] block-copy: refactor copy_range handling Kevin Wolf
2021-06-02 13:45 ` [PULL 20/20] docs/secure-coding-practices: Describe how to use 'null-co' block driver Kevin Wolf
2021-06-03 8:59 ` [PULL 00/20] Block layer patches 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=20210602134529.231756-1-kwolf@redhat.com \
--to=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 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).