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

On Wed, 04 Nov 2026 19:01:00 +0100, Denis V. Lunev wrote:
> dm-qcow2: fix merges not stopping the users of the images they change
> 
> Checking dm-qcow2 for the same problem showed that a merge does not
> stop everything using the images it changes (VSTOR-153049,
> VSTOR-153050):
> 
> - a backward merge of an inner image starts without pausing anything,
>   while reads enter through the top image. A read reaching the inner
>   image as the merge starts oopses on a NULL qio->ext (patch 2);
> 
> [...]

Applied to branch-rh10-6.12.0-211.52.1.22.x.vz10-ovz, will be released in rh10-6.12.0-211.52.1.22.18.vz10, thanks!

[1/5] dm-qcow2: fix a failed refcount table relocation leaking md pages
      https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/beada5e3721a
[2/5] dm-qcow2: fix backward merge of an inner image racing its reads
      https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/917b0f940acc
[3/5] dm-qcow2: fix SEEK_HOLE/SEEK_DATA using an image freed by a merge
      https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/5400a597e4d6
[4/5] dm-qcow2: fix SEEK_HOLE/SEEK_DATA hanging after a failed metadata read
      https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/334bce6208ed
[5/5] dm-qcow2: fix a refcount table relocation failing on a valid image
      https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/6f2dd6d659e1

-- 
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 18:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 18:01 Denis V. Lunev
2026-11-04 18:01 ` [Devel] [PATCH hci-8.1 v3 1/5] dm-qcow2: fix a failed refcount table relocation leaking md pages Denis V. Lunev
2026-11-04 18:52   ` no-reply
2026-11-04 18:01 ` [Devel] [PATCH hci-8.1 v3 2/5] dm-qcow2: fix backward merge of an inner image racing its reads Denis V. Lunev
2026-11-04 18:52   ` no-reply
2026-11-04 18:01 ` [Devel] [PATCH hci-8.1 v3 3/5] dm-qcow2: fix SEEK_HOLE/SEEK_DATA using an image freed by a merge Denis V. Lunev
2026-11-04 18:54   ` no-reply
2026-11-04 18:01 ` [Devel] [PATCH hci-8.1 v3 4/5] dm-qcow2: fix SEEK_HOLE/SEEK_DATA hanging after a failed metadata read Denis V. Lunev
2026-11-04 18:55   ` no-reply
2026-11-04 18:01 ` [Devel] [PATCH hci-8.1 v3 5/5] dm-qcow2: fix a refcount table relocation failing on a valid image Denis V. Lunev
2026-11-04 18:55   ` no-reply
2026-11-04 18:30 ` 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=179381700712.2735802.13009025695192662868.b4-ty@b4 \
    --to=khorenko@virtuozzo.com \
    --cc=andrey.zhadchenko@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