OpenVZ / Virtuozzo kernel development (devel@openvz.org)
 help / color / mirror / Atom feed
From: no-reply@sashiko.virtuozzo.com
To: Alexander Ivanov <alexander.ivanov@virtuozzo.com>, den@openvz.org
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 v3 4/5] dm-ploop: reload metadata on resume
Date: Thu, 8 Oct 2026 14:18:36 +0000	[thread overview]
Message-ID: <010701a11be15c58-989348d6-3ca9-44df-82db-2ecb88894cb1-000000@eu-central-1.amazonses.com> (raw)
In-Reply-To: <20261008140333.614909-5-alexander.ivanov@virtuozzo.com>

> On "dmsetup reload" the new ploop reads metadata of the images in
> ploop_ctr(), but IO continues through the old ploop until the device
> is suspended. So the old ploop may change BAT and sizes of the delta
> files, and after resume the new ploop works with outdated metadata,
> e.g. allocates clusters already used by the old one or relies on a
> wrong file size. Also userspace may modify images of suspended device
> (e.g. merge zeroes BAT entries of the base delta, snapshot creation
> trims the tail of the top delta).
> 
> Reload all the metadata in ploop_preresume(): re-read header of the top
> delta, BAT of every delta and sizes of delta files, and rebuild BAT
> tree and holes_bitmap from scratch. On error the old metadata is kept
> and resume fails.
> 
> Skip the in-use signature check on reload, as the image is already
> [ ... ]
> 
> https://virtuozzo.atlassian.net/browse/VSTOR-148171
> Feature: dm-ploop: ploop target driver
> 
> Signed-off-by: Alexander Ivanov <alexander.ivanov@virtuozzo.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.vzint.dev/#/patchset/20261008140333.614909-1-alexander.ivanov@virtuozzo.com?part=4


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

  reply	other threads:[~2026-10-08 14:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08 14:03 [Devel] [PATCH hci-8.1 v3 0/5] dm-ploop: truncate unused tail of top delta on suspend Alexander Ivanov
2026-10-08 14:03 ` [Devel] [PATCH hci-8.1 v3 1/5] dm-ploop: fix lost wakeup in ploop_allocator() Alexander Ivanov
2026-10-08 14:07   ` no-reply
2026-10-08 16:51   ` Denis V. Lunev
2026-10-08 14:03 ` [Devel] [PATCH hci-8.1 v3 2/5] dm-ploop: set delta is_raw before applying its mappings Alexander Ivanov
2026-10-08 14:09   ` no-reply
2026-10-08 16:51   ` Denis V. Lunev
2026-10-09  6:28   ` Alexander Ivanov
2026-10-08 14:03 ` [Devel] [PATCH hci-8.1 v3 3/5] dm-ploop: factor out ploop_read_delta() from ploop_add_delta() Alexander Ivanov
2026-10-08 14:08   ` no-reply
2026-10-08 16:51   ` Denis V. Lunev
2026-10-08 14:03 ` [Devel] [PATCH hci-8.1 v3 4/5] dm-ploop: reload metadata on resume Alexander Ivanov
2026-10-08 14:18   ` no-reply [this message]
2026-10-08 16:51   ` Denis V. Lunev
2026-10-08 14:03 ` [Devel] [PATCH hci-8.1 v3 5/5] dm-ploop: truncate unused tail of top delta on suspend Alexander Ivanov
2026-10-08 14:15   ` no-reply
2026-10-08 16:51   ` Denis V. Lunev

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=010701a11be15c58-989348d6-3ca9-44df-82db-2ecb88894cb1-000000@eu-central-1.amazonses.com \
    --to=no-reply@sashiko.virtuozzo.com \
    --cc=alexander.ivanov@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