f1eed34ac7
This version includes both the AioContext lock and the block graph lock, so there might be some deadlocks lurking. It's not possible to disable the block graph lock like was done in QEMU 8.1, because there are no changes like the function bdrv_schedule_unref() that require it. QEMU 9.0 will finally get rid of the AioContext locking. During live-restore with a VirtIO SCSI drive with iothread there is a known racy deadlock related to the AioContext lock. Not new [1], but not sure if more likely now. Should be fixed in QEMU 9.0. The block graph lock comes with annotations that can be checked by clang's TSA. This required changes to the block drivers, i.e. alloc-track, pbs, zeroinit as well as taking the appropriate locks in pve-backup, savevm-async, vma-reader. Local variable shadowing is prohibited via a compiler flag now, required slight adaptation in vma.c. Major changes only affect alloc-track: * It is not possible to call a generated co-wrapper like bdrv_get_info() while holding the block graph lock exclusively [0], which does happen during initialization of alloc-track when the backing hd is set and the refresh_limits driver callback is invoked. The bdrv_get_info() call to get the cluster size is moved to directly after opening the file child in track_open(). The important thing is that at least the request alignment for the write target is used, because then the RMW cycle in bdrv_pwritev will gather enough data from the backing file. Partial cluster allocations in the target are not a fundamental issue, because the driver returns its allocation status based on the bitmap, so any other data that maps to the same cluster will still be copied later by a stream job (or during writes to that cluster). * Replacing the node cannot be done in the track_co_change_backing_file() callback, because it is a coroutine and cannot hold the block graph lock exclusively. So it is moved to the stream job itself with the auto-remove option not having an effect anymore (qemu-server would always set it anyways). In the future, there could either be a special option for the stream job, or maybe the upcoming blockdev-replace QMP command can be used. Replacing the backing child is actually already done in the stream job, so no need to do it in the track_co_change_backing_file() callback. It also cannot be called from a coroutine. Looking at the implementation in the qcow2 driver, it doesn't seem to be intended to change the backing child itself, just update driver-internal state. Other changes: * alloc-track: Error out early when used without auto-remove. Since replacing the node now happens in the stream job, where the option cannot be read from (it's internal to the driver), it will always be treated as 'on'. Makes sure to have users beside qemu-server notice the change (should they even exist). The option can be fully dropped in the future while adding a version guard in qemu-server. * alloc-track: Avoid seemingly superfluous child permission update. Doesn't seem necessary nowadays (maybe after commit "alloc-track: fix deadlock during drop" where the dropping is not rescheduled and delayed anymore or some upstream change). Replacing the block node will already update the permissions of the new node (which was the file child before). Should there really be some issue, instead of having a drop state, this could also be just based off the fact whether there is still a backing child. Dumping the cumulative (shared) permissions for the BDS with a debug print yields the same values after this patch and with QEMU 8.1, namely 3 and 5. * PBS block driver: compile unconditionally. Proxmox VE always needs it and something in the build process changed to make it not enabled by default. Probably would need to move the build option to meson otherwise. * backup: job unreferencing during cleanup needs to happen outside of coroutine, so it was moved to before invoking the clean * mirror: Cherry-pick stable fix to avoid potential deadlock. * savevm-async: migrate_init now can fail, so propagate potential error. * savevm-async: compression counters are not accessible outside migration/ram-compress now, so drop code that prophylactically set it to zero. [0]: https://lore.kernel.org/qemu-devel/220be383-3b0d-4938-b584-69ad214e5d5d@proxmox.com/ [1]: https://lore.kernel.org/qemu-devel/e13b488e-bf13-44f2-acca-e724d14f43fd@proxmox.com/ Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
163 lines
5.4 KiB
Diff
163 lines
5.4 KiB
Diff
From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
|
|
From: Fabian Ebner <f.ebner@proxmox.com>
|
|
Date: Tue, 17 May 2022 09:46:02 +0200
|
|
Subject: [PATCH] Revert "block/rbd: implement bdrv_co_block_status"
|
|
|
|
During backup, bdrv_co_block_status is called for each block copy
|
|
chunk. When RBD is used, the current implementation with
|
|
rbd_diff_iterate2() using whole_object=true takes about linearly more
|
|
time, depending on the image size. Since there are linearly more
|
|
chunks, the slowdown is quadratic, becoming unacceptable for large
|
|
images (starting somewhere between 500-1000 GiB in my testing).
|
|
|
|
This reverts commit 0347a8fd4c3faaedf119be04c197804be40a384b as a
|
|
stop-gap measure, until it's clear how to make the implemenation
|
|
more efficient.
|
|
|
|
Upstream bug report:
|
|
https://gitlab.com/qemu-project/qemu/-/issues/1026
|
|
|
|
Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
|
|
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
|
|
---
|
|
block/rbd.c | 112 ----------------------------------------------------
|
|
1 file changed, 112 deletions(-)
|
|
|
|
diff --git a/block/rbd.c b/block/rbd.c
|
|
index 347b121626..e61b359b97 100644
|
|
--- a/block/rbd.c
|
|
+++ b/block/rbd.c
|
|
@@ -108,12 +108,6 @@ typedef struct RBDTask {
|
|
int64_t ret;
|
|
} RBDTask;
|
|
|
|
-typedef struct RBDDiffIterateReq {
|
|
- uint64_t offs;
|
|
- uint64_t bytes;
|
|
- bool exists;
|
|
-} RBDDiffIterateReq;
|
|
-
|
|
static int qemu_rbd_connect(rados_t *cluster, rados_ioctx_t *io_ctx,
|
|
BlockdevOptionsRbd *opts, bool cache,
|
|
const char *keypairs, const char *secretid,
|
|
@@ -1460,111 +1454,6 @@ static ImageInfoSpecific *qemu_rbd_get_specific_info(BlockDriverState *bs,
|
|
return spec_info;
|
|
}
|
|
|
|
-/*
|
|
- * rbd_diff_iterate2 allows to interrupt the exection by returning a negative
|
|
- * value in the callback routine. Choose a value that does not conflict with
|
|
- * an existing exitcode and return it if we want to prematurely stop the
|
|
- * execution because we detected a change in the allocation status.
|
|
- */
|
|
-#define QEMU_RBD_EXIT_DIFF_ITERATE2 -9000
|
|
-
|
|
-static int qemu_rbd_diff_iterate_cb(uint64_t offs, size_t len,
|
|
- int exists, void *opaque)
|
|
-{
|
|
- RBDDiffIterateReq *req = opaque;
|
|
-
|
|
- assert(req->offs + req->bytes <= offs);
|
|
- /*
|
|
- * we do not diff against a snapshot so we should never receive a callback
|
|
- * for a hole.
|
|
- */
|
|
- assert(exists);
|
|
-
|
|
- if (!req->exists && offs > req->offs) {
|
|
- /*
|
|
- * we started in an unallocated area and hit the first allocated
|
|
- * block. req->bytes must be set to the length of the unallocated area
|
|
- * before the allocated area. stop further processing.
|
|
- */
|
|
- req->bytes = offs - req->offs;
|
|
- return QEMU_RBD_EXIT_DIFF_ITERATE2;
|
|
- }
|
|
-
|
|
- if (req->exists && offs > req->offs + req->bytes) {
|
|
- /*
|
|
- * we started in an allocated area and jumped over an unallocated area,
|
|
- * req->bytes contains the length of the allocated area before the
|
|
- * unallocated area. stop further processing.
|
|
- */
|
|
- return QEMU_RBD_EXIT_DIFF_ITERATE2;
|
|
- }
|
|
-
|
|
- req->bytes += len;
|
|
- req->exists = true;
|
|
-
|
|
- return 0;
|
|
-}
|
|
-
|
|
-static int coroutine_fn qemu_rbd_co_block_status(BlockDriverState *bs,
|
|
- bool want_zero, int64_t offset,
|
|
- int64_t bytes, int64_t *pnum,
|
|
- int64_t *map,
|
|
- BlockDriverState **file)
|
|
-{
|
|
- BDRVRBDState *s = bs->opaque;
|
|
- int status, r;
|
|
- RBDDiffIterateReq req = { .offs = offset };
|
|
- uint64_t features, flags;
|
|
-
|
|
- assert(offset + bytes <= s->image_size);
|
|
-
|
|
- /* default to all sectors allocated */
|
|
- status = BDRV_BLOCK_DATA | BDRV_BLOCK_OFFSET_VALID;
|
|
- *map = offset;
|
|
- *file = bs;
|
|
- *pnum = bytes;
|
|
-
|
|
- /* check if RBD image supports fast-diff */
|
|
- r = rbd_get_features(s->image, &features);
|
|
- if (r < 0) {
|
|
- return status;
|
|
- }
|
|
- if (!(features & RBD_FEATURE_FAST_DIFF)) {
|
|
- return status;
|
|
- }
|
|
-
|
|
- /* check if RBD fast-diff result is valid */
|
|
- r = rbd_get_flags(s->image, &flags);
|
|
- if (r < 0) {
|
|
- return status;
|
|
- }
|
|
- if (flags & RBD_FLAG_FAST_DIFF_INVALID) {
|
|
- return status;
|
|
- }
|
|
-
|
|
- r = rbd_diff_iterate2(s->image, NULL, offset, bytes, true, true,
|
|
- qemu_rbd_diff_iterate_cb, &req);
|
|
- if (r < 0 && r != QEMU_RBD_EXIT_DIFF_ITERATE2) {
|
|
- return status;
|
|
- }
|
|
- assert(req.bytes <= bytes);
|
|
- if (!req.exists) {
|
|
- if (r == 0) {
|
|
- /*
|
|
- * rbd_diff_iterate2 does not invoke callbacks for unallocated
|
|
- * areas. This here catches the case where no callback was
|
|
- * invoked at all (req.bytes == 0).
|
|
- */
|
|
- assert(req.bytes == 0);
|
|
- req.bytes = bytes;
|
|
- }
|
|
- status = BDRV_BLOCK_ZERO | BDRV_BLOCK_OFFSET_VALID;
|
|
- }
|
|
-
|
|
- *pnum = req.bytes;
|
|
- return status;
|
|
-}
|
|
-
|
|
static int64_t coroutine_fn qemu_rbd_co_getlength(BlockDriverState *bs)
|
|
{
|
|
BDRVRBDState *s = bs->opaque;
|
|
@@ -1800,7 +1689,6 @@ static BlockDriver bdrv_rbd = {
|
|
#ifdef LIBRBD_SUPPORTS_WRITE_ZEROES
|
|
.bdrv_co_pwrite_zeroes = qemu_rbd_co_pwrite_zeroes,
|
|
#endif
|
|
- .bdrv_co_block_status = qemu_rbd_co_block_status,
|
|
|
|
.bdrv_snapshot_create = qemu_rbd_snap_create,
|
|
.bdrv_snapshot_delete = qemu_rbd_snap_remove,
|