All Virtuozzo development lists (kernel + QEMU)
 help / color / mirror / Atom feed
From: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: svt-core@virtuozzo.com
Subject: Re: [PATCH hci-dev 0/2] qcow2, block: fix reopen of a dirty read-only node and of a corrupt node #VSTOR-140073
Date: Thu, 5 Nov 2026 17:31:53 +0200	[thread overview]
Message-ID: <3e65b5c0-6553-4722-885b-3b868734a07b@virtuozzo.com> (raw)
In-Reply-To: <20261104144113.1587724-1-den@openvz.org>

On 11/4/26 4:41 PM, Denis V. Lunev wrote:
> These are patches 1 and 2 of the hci-8.0 posting of September 16, merged
> upstream as af28b65fae6 and efe98c2a093. The repair of a dirty image
> that becomes writable is not part of this.
> 
> - A read-only to read-only reopen of a dirty qcow2 image fails, or
>   aborts on the BLK_PERM_WRITE assertion in bdrv_co_write_req_prepare()
>   when the file node below is writable.
> - A reopen of a node which qcow2_signal_corruption() left without a
>   driver crashes QEMU. commit_clean() reopens the base of a commit job
>   this way.
> 
> Patch 1 is a clean pick. Patch 2 differs only in 060.out: HMP qemu-io on
> this tree prints a failed read on the monitor instead of returning it.
> 
> Tested on dev-cl04. Unpatched hci-dev fails the new 039 and 060 cases
> with that assertion and with a segfault; with the series both pass. The
> other reopen iotests, qcow2 and raw, give the same result with and
> without it.
> 
> Denis V. Lunev (2):
>   qcow2: do not clear the dirty bit when reopening a read-only node
>     #VSTOR-140073
>   block: reject a reopen of an unusable node instead of crashing
>     #VSTOR-140073
> 
>  block.c                    | 14 ++++++++++-
>  block/qcow2.c              |  8 +++---
>  tests/qemu-iotests/039     | 50 ++++++++++++++++++++++++++++++++++++++
>  tests/qemu-iotests/039.out | 20 +++++++++++++++
>  tests/qemu-iotests/060     | 30 +++++++++++++++++++++++
>  tests/qemu-iotests/060.out | 13 ++++++++++
>  6 files changed, 131 insertions(+), 4 deletions(-)
> 
> 
> base-commit: ca7715cc68cdd379b9fbe32d794408bd87a6677e

Ack
Applied to hci-dev

      parent reply	other threads:[~2026-11-05 15:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 14:41 Denis V. Lunev
2026-11-04 14:41 ` [PATCH hci-dev 1/2] qcow2: do not clear the dirty bit when reopening a read-only " Denis V. Lunev
2026-11-04 14:43   ` no-reply
2026-11-04 14:41 ` [PATCH hci-dev 2/2] block: reject a reopen of an unusable node instead of crashing #VSTOR-140073 Denis V. Lunev
2026-11-04 14:43   ` no-reply
2026-11-05 15:31 ` Andrey Drobyshev [this message]

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=3e65b5c0-6553-4722-885b-3b868734a07b@virtuozzo.com \
    --to=andrey.drobyshev@virtuozzo.com \
    --cc=den@openvz.org \
    --cc=svt-core@virtuozzo.com \
    /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.