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 0/3] dm-ploop: fix writes to a read-only device hanging the host
Date: Tue, 10 Nov 2026 18:11:28 +0100 [thread overview]
Message-ID: <179433068800.3552165.16714872731769532997.b4-ty@b4> (raw)
In-Reply-To: <20261109190604.1850504-1-den@openvz.org>
On Mon, 09 Nov 2026 20:06:01 +0100, Denis V. Lunev wrote:
> dm-ploop: fix writes to a read-only device hanging the host
>
> A write that reaches a read-only ploop device never completes: the
> writer hangs in D state, and after a buffered write every later sync on
> the host hangs behind it until a reboot. Such writes come from a device
> stacked on top. libploop leaves the partition of "ploop mount -r"
> writable, which the ploop side fixes in openvz/ploop.ovz PR 513, and
> libvzctl attaches a backup disk to a Container that way and mounts it
> read-write (VSTOR-154096).
>
> [...]
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.20.vz10, thanks!
[1/3] dm-ploop: factor out ploop_dispatch_md_waiters()
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/f63736a643a0
[2/3] dm-ploop: fix pios stuck in md->wait_llist after a failed BAT update
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/92c732d66bea
[3/3] dm-ploop: fail writes to a read-only device
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/7028a441789c
--
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:12 UTC|newest]
Thread overview: 12+ 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/3] dm-ploop: factor out ploop_dispatch_md_waiters() Denis V. Lunev
2026-11-09 19:15 ` no-reply
2026-11-10 17:11 ` Konstantin Khorenko
2026-11-09 19:06 ` [Devel] [PATCH hci-8.1 2/3] dm-ploop: fix pios stuck in md->wait_llist after a failed BAT update Denis V. Lunev
2026-11-09 19:18 ` no-reply
2026-11-10 17:11 ` Konstantin Khorenko
2026-11-09 19:06 ` [Devel] [PATCH hci-8.1 3/3] dm-ploop: fail writes to a read-only device Denis V. Lunev
2026-11-09 19:19 ` no-reply
2026-11-10 17:11 ` Konstantin Khorenko
2026-11-10 17:11 ` [Devel] [PATCH hci-8.1 0/3] dm-ploop: fix writes to a read-only device hanging the host Konstantin Khorenko
2026-11-10 17:11 ` 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=179433068800.3552165.16714872731769532997.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 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.