From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 0/2] dm-ploop: fix writes held on ENOSPC never being retried
Date: Tue, 10 Nov 2026 18:03:39 +0100 [thread overview]
Message-ID: <179433021952.3552165.1138458329605355940.b4-review@b4> (raw)
In-Reply-To: <20261109190657.1851487-1-den@openvz.org>
I won't apply this version, please send v2 with the changes below.
On Mon, 9 Nov 2026 20:06:55 +0100, Denis V. Lunev wrote:
> dm-ploop: fix writes held on ENOSPC never being retried
The code of both patches is right. For v2:
1. Patch 1: cancel event_work in ploop_destroy() next to the timer.
2. Patch 1 message: name mod_timer() after the wants_suspend test as
the race, not the lockless test, and say what the user gets.
3. Patch 2 message: drop the wrong reason given for xchg().
4. Patch 2 message: start a new paragraph at "The held writes are
retried only...".
5. Cover letter: drop the vmcore paragraph and the measured numbers.
> Found in a vmcore: 16 writers in D state, submit_enospc set, all 16
> pios on enospc_pios, the timer expired 12 s before the crash.
Item 5. The cover letter goes into each commit as the "Patchset
description", so this ends up in the git log. How the bug was found
and the timings belong in VSTOR-154182, not in a commit message.
> Tested on 6.12.0-211.52.1.22.19.vz10, dm-ploop built out of tree:
> - 16 O_DIRECT writers held on a full host ext4, then the space freed
> with no other I/O on the device. Stock: still stuck after 60 s, one
> unrelated read releases them. With the series: done 8 s after the
> space is freed, on the next timer tick;
> - ploop test suite, make -j48 test on dev-cl04, green for ploop and
> qcow2 with this series together with the VSTOR-154096 one.
Same here: say what was tested (writers held on a full image, space
freed with no other I/O, they finish when enospc_timer next expires;
the ploop test suite passes), without the numbers and the host name.
Separate patch, not for this series: dm-qcow2 has the same hole.
qcow2_tgt_destroy() stops neither enospc_timer nor event_work, the
mod_timer() in the ENOSPC path runs after event_lock is dropped, and
presuspend uses timer_delete_sync_try() as well.
--
Konstantin Khorenko,
Virtuozzo Linux Kernel Team
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
prev parent reply other threads:[~2026-11-10 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 19:06 Denis V. Lunev
2026-11-09 19:06 ` [Devel] [PATCH hci-8.1 1/2] dm-ploop: stop enospc_timer in ploop_destroy() Denis V. Lunev
2026-11-09 19:17 ` no-reply
2026-11-10 17:03 ` Konstantin Khorenko
2026-11-09 19:06 ` [Devel] [PATCH hci-8.1 2/2] dm-ploop: fix the ENOSPC retry timer not waking the dispatcher Denis V. Lunev
2026-11-09 19:18 ` no-reply
2026-11-10 17:03 ` Konstantin Khorenko
2026-11-10 17:03 ` 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=179433021952.3552165.1138458329605355940.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 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.