All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Denis V. Lunev" <den@openvz.org>
To: qemu-devel@nongnu.org
Cc: den@openvz.org, qemu-block@nongnu.org, qemu-stable@nongnu.org,
	Kevin Wolf <kwolf@redhat.com>, Hanna Reitz <hreitz@redhat.com>,
	Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>,
	Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
Subject: [PATCH 04/13] block/preallocate: serialise the filter state
Date: Wed, 30 Sep 2026 18:49:50 +0200	[thread overview]
Message-ID: <20260930165000.303236-5-den@openvz.org> (raw)
In-Reply-To: <20260930165000.303236-1-den@openvz.org>

From: Denis V. Lunev <den@openvz.org>

The filter keeps the file length it has seen, the length it has
reserved and where the trailing zeroes start in plain fields, and
updates them with a read, a compare and a store. That was indivisible
while one node was driven by one AioContext. It is not any more:
virtio-blk with iothread-vq-mapping drives one node from several.

Two writers extending the file then both pass the compare, and the
smaller end lands last:

  writer A, [1G, 1G+64k)            writer B, [1G+64k, 1G+128k)
  --------------------------------  --------------------------------
  reads data_end 1G, 1G+64k > 1G
                                    reads data_end 1G, 1G+128k > 1G
                                    stores data_end = 1G+128k
  stores data_end = 1G+64k

Both writes are acknowledged, and data_end now sits below B's data.
Nothing raises it again except a later write ending beyond it, and
closing the image truncates the file to it, so B's data is cut off the
end. The last pair of extending writes before a shutdown is exactly
where this bites.

Take a mutex across handle_write() and preallocate_co_getlength(). The
remaining readers, apart from preallocate_co_truncate(), reach the
state from global state code with the node drained, where no request
is in flight.

Holding it cannot deadlock. A writer waiting for it has not reached
bs->file yet, so it owns nothing below the filter, and the only calls
made under it go to the child. preallocate_co_truncate() is left out
for that reason: growing the file waits for the requests in flight on
the child, and once the next patch issues the preallocation without
the mutex, one of those can be a preallocation that needs it back.

Signed-off-by: Denis V. Lunev <den@openvz.org>
Cc: qemu-stable@nongnu.org
CC: Kevin Wolf <kwolf@redhat.com>
CC: Hanna Reitz <hreitz@redhat.com>
CC: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
CC: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
---
 block/preallocate.c | 27 ++++++++++++++++++++++++---
 1 file changed, 24 insertions(+), 3 deletions(-)

diff --git a/block/preallocate.c b/block/preallocate.c
index 8cd98684f4..442cdb0176 100644
--- a/block/preallocate.c
+++ b/block/preallocate.c
@@ -76,6 +76,8 @@ typedef struct BDRVPreallocateState {
      * BLK_PERM_WRITE permissions on file child.
      */
 
+    CoMutex lock;
+
     /* Gives up the resize permission on children when parents don't need it */
     QEMUBH *drop_resize_bh;
 } BDRVPreallocateState;
@@ -155,6 +157,7 @@ static int preallocate_open(BlockDriverState *bs, QDict *options, int flags,
      * For this to work, mark them invalid.
      */
     preallocate_set_state(s, -EINVAL);
+    qemu_co_mutex_init(&s->lock);
     s->drop_resize_bh = qemu_bh_new(preallocate_drop_resize_bh, bs);
 
     ret = bdrv_open_file_child(NULL, options, "file", bs, errp);
@@ -324,8 +327,8 @@ static bool GRAPH_RDLOCK has_prealloc_perms(BlockDriverState *bs)
  * one bdrv_co_pwrite_zeroes() call.
  */
 static bool coroutine_fn GRAPH_RDLOCK
-handle_write(BlockDriverState *bs, int64_t offset, int64_t bytes,
-             bool want_merge_zero)
+handle_write_locked(BlockDriverState *bs, int64_t offset, int64_t bytes,
+                    bool want_merge_zero)
 {
     BDRVPreallocateState *s = bs->opaque;
     int64_t end = offset + bytes;
@@ -404,6 +407,20 @@ handle_write(BlockDriverState *bs, int64_t offset, int64_t bytes,
     return want_merge_zero;
 }
 
+static bool coroutine_fn GRAPH_RDLOCK
+handle_write(BlockDriverState *bs, int64_t offset, int64_t bytes,
+             bool want_merge_zero)
+{
+    BDRVPreallocateState *s = bs->opaque;
+    bool ret;
+
+    qemu_co_mutex_lock(&s->lock);
+    ret = handle_write_locked(bs, offset, bytes, want_merge_zero);
+    qemu_co_mutex_unlock(&s->lock);
+
+    return ret;
+}
+
 static int coroutine_fn GRAPH_RDLOCK
 preallocate_co_pwrite_zeroes(BlockDriverState *bs, int64_t offset,
                              int64_t bytes, BdrvRequestFlags flags)
@@ -506,8 +523,11 @@ preallocate_co_getlength(BlockDriverState *bs)
     int64_t ret;
     BDRVPreallocateState *s = bs->opaque;
 
+    qemu_co_mutex_lock(&s->lock);
     if (s->data_end >= 0) {
-        return s->data_end;
+        ret = s->data_end;
+        qemu_co_mutex_unlock(&s->lock);
+        return ret;
     }
 
     ret = bdrv_co_getlength(bs->file->bs);
@@ -515,6 +535,7 @@ preallocate_co_getlength(BlockDriverState *bs)
     if (has_prealloc_perms(bs)) {
         preallocate_set_state(s, ret);
     }
+    qemu_co_mutex_unlock(&s->lock);
 
     return ret;
 }
-- 
2.53.0



  parent reply	other threads:[~2026-09-30 16:51 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30 16:49 [PATCH 00/13] block: fix data loss in the preallocate filter Denis V. Lunev
2026-09-30 16:49 ` [PATCH 01/13] block/file-posix: drop the XFS workaround for post-EOF fallocate Denis V. Lunev
2026-10-02 16:16   ` Andrey Drobyshev
2026-09-30 16:49 ` [PATCH 02/13] block/preallocate: keep zero_start above written data Denis V. Lunev
2026-10-02 16:16   ` Andrey Drobyshev
2026-09-30 16:49 ` [PATCH 03/13] block/preallocate: collect the state assignments in one place Denis V. Lunev
2026-10-02 16:16   ` Andrey Drobyshev
2026-09-30 16:49 ` Denis V. Lunev [this message]
2026-10-02 16:16   ` [PATCH 04/13] block/preallocate: serialise the filter state Andrey Drobyshev
2026-09-30 16:49 ` [PATCH 05/13] block/preallocate: hold back writes into a preallocation in flight Denis V. Lunev
2026-10-02 16:16   ` Andrey Drobyshev
2026-09-30 16:49 ` [PATCH 06/13] iotests/298: add testcase for async writes with preallocation filter Denis V. Lunev
2026-09-30 16:49 ` [PATCH 07/13] tests/unit: prefix the iothread test helper Denis V. Lunev
2026-10-05 20:06   ` Eric Blake
2026-09-30 16:49 ` [PATCH 08/13] qemu-io: accept --object iothread Denis V. Lunev
2026-10-05 20:11   ` Eric Blake
2026-09-30 16:49 ` [PATCH 09/13] qemu-io: add -t to run an aio request in a named iothread Denis V. Lunev
2026-10-05 20:28   ` Eric Blake
2026-09-30 16:49 ` [PATCH 10/13] qemu-io: add -g to write past the end of the image Denis V. Lunev
2026-10-05 20:36   ` Eric Blake
2026-09-30 16:49 ` [PATCH 11/13] block/blkdebug: make a breakpoint work across AioContexts Denis V. Lunev
2026-10-05 20:42   ` Eric Blake
2026-09-30 16:49 ` [PATCH 12/13] block: add blkdebug events for a write before it is tracked Denis V. Lunev
2026-10-05 20:45   ` Eric Blake
2026-09-30 16:49 ` [PATCH 13/13] iotests/298: cover the preallocation races Denis V. Lunev
2026-10-05 21:06   ` Eric Blake

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=20260930165000.303236-5-den@openvz.org \
    --to=den@openvz.org \
    --cc=andrey.drobyshev@virtuozzo.com \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=vsementsov@yandex-team.ru \
    /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.