From: "Denis V. Lunev" <den@openvz.org>
To: khorenko@virtuozzo.com
Cc: devel@openvz.org
Subject: [Devel] [PATCH hci-8.1 v2 0/2] dm-ploop: fix writes held on ENOSPC never being retried
Date: Tue, 10 Nov 2026 20:00:31 +0100 [thread overview]
Message-ID: <20261110190033.2976967-1-den@openvz.org> (raw)
A write that fails with ENOSPC on the image is held and retried by
enospc_timer, so that I/O resumes once space is freed. Nothing wakes
the dispatcher for the retry, so the held writes stay in D state until
other I/O reaches the device (VSTOR-154182). The destructor is also
made to stop the timer and the event work.
Tested: writers held on a full image finish when enospc_timer next
expires after the space is freed; the ploop test suite passes.
v2: cancel event_work in ploop_destroy(), reword the messages.
v1: http://lore.virtuozzo.com/kernel/20261109190657.1851487-1-den@openvz.org/
Denis V. Lunev (2):
dm-ploop: stop enospc_timer and event_work in ploop_destroy()
dm-ploop: fix the ENOSPC retry timer not waking the dispatcher
drivers/md/dm-ploop-map.c | 9 +++++----
drivers/md/dm-ploop-target.c | 2 ++
2 files changed, 7 insertions(+), 4 deletions(-)
--
2.53.0
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next reply other threads:[~2026-11-10 19:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 19:00 Denis V. Lunev [this message]
2026-11-10 19:00 ` [Devel] [PATCH hci-8.1 v2 1/2] dm-ploop: stop enospc_timer and event_work in ploop_destroy() Denis V. Lunev
2026-11-10 19:05 ` no-reply
2026-11-12 12:50 ` Konstantin Khorenko
2026-11-10 19:00 ` [Devel] [PATCH hci-8.1 v2 2/2] dm-ploop: fix the ENOSPC retry timer not waking the dispatcher Denis V. Lunev
2026-11-10 19:02 ` no-reply
2026-11-12 12:50 ` Konstantin Khorenko
2026-11-12 12:50 ` [Devel] [PATCH hci-8.1 v2 0/2] dm-ploop: fix writes held on ENOSPC never being retried Konstantin Khorenko
2026-11-12 12:50 ` 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=20261110190033.2976967-1-den@openvz.org \
--to=den@openvz.org \
--cc=devel@openvz.org \
--cc=khorenko@virtuozzo.com \
/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.