All Virtuozzo development lists (kernel + QEMU)
 help / color / mirror / Atom feed
From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Alexander Ivanov <alexander.ivanov@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 v11 00/10] dm-qcow2: truncate unused tail of image on suspend
Date: Mon, 09 Nov 2026 16:42:38 +0100	[thread overview]
Message-ID: <179423895898.3398823.4144864009513938243.b4-review@b4> (raw)
In-Reply-To: <20261109140143.1408038-1-alexander.ivanov@virtuozzo.com>

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

On 11/9/26 15:01, Alexander Ivanov wrote:
> Alexander Ivanov (10):
>   dm-qcow2: add qcow2_md_page_read_sync() helper
>   dm-qcow2: drop duplicate prefix from QC_ERR/QC_INFO messages
>   dm-qcow2: extend the file for a new refblock in allocate_cluster()
>   dm-qcow2: complete wbd before ending the data qio
>   dm-qcow2: flush lower md before clearing dirty bit on merge failure
>   dm-qcow2: keep the dirty bit of an image that needs check
>   dm-qcow2: flag the image for check if reftable relocation fails late
>   dm-qcow2: leak clusters allocated for a failed L1/L2 writeback
>   dm-qcow2: retry R1/R2 writeback that failed with ENOSPC
>   dm-qcow2: truncate unused tail of image on suspend

What to change for v12:

1. Patch 8, code: in prepare_l1l2_allocation(), queue the qio that
   allocates an L2-table cluster for an L1 update on
   l1.md->wbd->dependent_list instead of l1.md->wait_list, so a failed
   L1 writeback ends it with the error instead of sending it back to
   allocate another cluster. The new loop in complete_wbd() then has to
   skip a qio without ext.
2. Patch 8, commit message: say what is leaked: one cluster per failed
   L1/L2 write of a request.
3. Patch 9, comment and commit message: a page that failed before the
   flush gets up to two attempts during it, not "once" or "one more
   try". MD_DIRTY is dropped when the write is submitted, not by the
   failure.
4. Patch 9, commit message: say that with patch 8 a request whose L2
   write keeps failing with ENOSPC leaks one data cluster on every
   resubmission, until the space is back.
5. Patch 10, commit message: the scan is skipped on md_writeback_error,
   which a late reftable relocation failure (patch 7) sets too, not only
   a failed R1/R2 writeback.
6. Cover letter: the patch 9 line of the changelog says "once" as well,
   fix it as in item 3.

Separate patches, not needed for v12:

1. A REQ_OP_FLUSH whose fsync fails with ENOSPC ends with
   BLK_STS_NOSPC, and qrq_endio() hits WARN_ON_ONCE(!op_is_write())
   for it. This is older than the series.

-- 
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-09 15:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 14:01 Alexander Ivanov
2026-11-09 14:01 ` [Devel] [PATCH hci-8.1 v11 01/10] dm-qcow2: add qcow2_md_page_read_sync() helper Alexander Ivanov
2026-11-09 14:06   ` no-reply
2026-11-09 14:01 ` [Devel] [PATCH hci-8.1 v11 02/10] dm-qcow2: drop duplicate prefix from QC_ERR/QC_INFO messages Alexander Ivanov
2026-11-09 14:05   ` no-reply
2026-11-09 14:01 ` [Devel] [PATCH hci-8.1 v11 03/10] dm-qcow2: extend the file for a new refblock in allocate_cluster() Alexander Ivanov
2026-11-09 14:06   ` no-reply
2026-11-09 14:01 ` [Devel] [PATCH hci-8.1 v11 04/10] dm-qcow2: complete wbd before ending the data qio Alexander Ivanov
2026-11-09 14:09   ` no-reply
2026-11-09 14:01 ` [Devel] [PATCH hci-8.1 v11 05/10] dm-qcow2: flush lower md before clearing dirty bit on merge failure Alexander Ivanov
2026-11-09 14:08   ` no-reply
2026-11-09 14:01 ` [Devel] [PATCH hci-8.1 v11 06/10] dm-qcow2: keep the dirty bit of an image that needs check Alexander Ivanov
2026-11-09 14:11   ` no-reply
2026-11-09 14:01 ` [Devel] [PATCH hci-8.1 v11 07/10] dm-qcow2: flag the image for check if reftable relocation fails late Alexander Ivanov
2026-11-09 14:11   ` no-reply
2026-11-09 15:42   ` Konstantin Khorenko
2026-11-09 14:01 ` [Devel] [PATCH hci-8.1 v11 08/10] dm-qcow2: leak clusters allocated for a failed L1/L2 writeback Alexander Ivanov
2026-11-09 14:14   ` no-reply
2026-11-09 14:36     ` Alexander Ivanov
2026-11-09 15:42   ` Konstantin Khorenko
2026-11-09 14:01 ` [Devel] [PATCH hci-8.1 v11 09/10] dm-qcow2: retry R1/R2 writeback that failed with ENOSPC Alexander Ivanov
2026-11-09 14:16   ` no-reply
2026-11-09 14:39     ` Alexander Ivanov
2026-11-09 15:42   ` Konstantin Khorenko
2026-11-09 14:01 ` [Devel] [PATCH hci-8.1 v11 10/10] dm-qcow2: truncate unused tail of image on suspend Alexander Ivanov
2026-11-09 14:18   ` no-reply
2026-11-09 14:47     ` Alexander Ivanov
2026-11-09 15:42   ` Konstantin Khorenko
2026-11-09 15:42 ` Konstantin Khorenko [this message]
2026-11-09 15:54 ` [Devel] [PATCH hci-8.1 v11 00/10] " Konstantin Khorenko

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=179423895898.3398823.4144864009513938243.b4-review@b4 \
    --to=khorenko@virtuozzo.com \
    --cc=alexander.ivanov@virtuozzo.com \
    --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 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.