OpenVZ / Virtuozzo kernel development (devel@openvz.org)
 help / color / mirror / Atom feed
From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 v2 0/3] dm-qcow2: fix merges not stopping the users of the images they change
Date: Wed, 04 Nov 2026 17:59:49 +0100	[thread overview]
Message-ID: <179381158915.2686233.9485645811464314374.b4-review@b4> (raw)
In-Reply-To: <20261103090813.166986-1-den@openvz.org>

I won't apply this version, please send v2 with the changes below.

On 11/3/26 10:08, Denis V. Lunev wrote:
> Denis V. Lunev (3):
>   dm-qcow2: fix a failed refcount table relocation leaking md pages
>   dm-qcow2: fix backward merge of an inner image racing its reads
>   dm-qcow2: fix SEEK_HOLE/SEEK_DATA using an image freed by a merge

What to change for v2:

1. Patch 1, code: after a successful header write, the error gotos
   must not free the new md pages. Send them to a label after the free
   loop that only returns -EIO, and update the "Note for a future
   reader" to match.
2. Patch 2, code comment: write "no guest writes" instead of "no
   writes".
3. Patch 2, commit message: say that guest I/O to the top image is now
   paused for the inflight ref switch when a merge of an inner image
   starts or stops.
4. Patch 3, commit message: say that merge_backward complete now waits
   for a running seek while it holds ctl_mutex.
5. Cover letter: fix the bullet on patch 2 quoted below.

Separate patches, not needed for v2:

6. relocate_refcount_table(): the refcount group of the new reftable
   gets no refblock when the table fills that whole group.
7. qcow2_llseek_hole(): a seek waits forever when one of its md page
   reads fails.

The details are in the replies to each patch.

> - a backward merge of an inner image pauses that image, while reads
>   enter through the top one. A read reaching the inner image as the
>   merge starts oopses on a NULL qio->ext (patch 2);

Item 5: before the series the start of an inner merge paused nothing,
only the stop paused the inner image. Say that the start paused nothing.

-- 
Konstantin Khorenko,
Virtuozzo Linux Kernel Team

_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel

      parent reply	other threads:[~2026-11-04 17:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03  9:08 Denis V. Lunev
2026-11-03  9:08 ` [Devel] [PATCH hci-8.1 v2 1/3] dm-qcow2: fix a failed refcount table relocation leaking md pages Denis V. Lunev
2026-11-03  9:13   ` no-reply
2026-11-03  9:27     ` Denis V. Lunev
2026-11-04 16:59   ` Konstantin Khorenko
2026-11-03  9:08 ` [Devel] [PATCH hci-8.1 v2 2/3] dm-qcow2: fix backward merge of an inner image racing its reads Denis V. Lunev
2026-11-03  9:13   ` no-reply
2026-11-04 16:59   ` Konstantin Khorenko
2026-11-03  9:08 ` [Devel] [PATCH hci-8.1 v2 3/3] dm-qcow2: fix SEEK_HOLE/SEEK_DATA using an image freed by a merge Denis V. Lunev
2026-11-03  9:15   ` no-reply
2026-11-04 16:59   ` Konstantin Khorenko
2026-11-04 13:15 ` [Devel] [PATCH hci-8.1 v2 0/3] dm-qcow2: fix merges not stopping the users of the images they change Andrey Zhadchenko
2026-11-04 16:59 ` Konstantin Khorenko [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=179381158915.2686233.9485645811464314374.b4-review@b4 \
    --to=khorenko@virtuozzo.com \
    --cc=den@openvz.org \
    --cc=devel@openvz.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