From: Andrey Zhadchenko <andrey.zhadchenko@virtuozzo.com>
To: alexander.ivanov@virtuozzo.com
Cc: devel@openvz.org
Subject: [Devel] [PATCH 0/5] dm/push_backup: event fd interface and fixes
Date: Tue, 3 Nov 2026 02:38:44 +0300 [thread overview]
Message-ID: <20261102233849.613155-1-andrey.zhadchenko@virtuozzo.com> (raw)
The push_backup target currently makes the backup tool wait for the next
cluster range inside the "push_backup_read" target message. dm runs
target_message() under dm_get_live_table(), i.e. with md->io_barrier SRCU
read-locked, so while the tool sleeps there anything that needs
synchronize_srcu(&md->io_barrier) on that device is stuck: suspend, table
reload/remove and dm_internal_suspend_fast() from "@stats_create". An
unrelated dm-stats user hangs, and everything that later queues behind
md->suspend_lock hangs with it.
Patch 5 adds a file descriptor based interface instead. The tool gets an
anon inode fd via the "push_backup_get_fd" message and then uses plain
read()/write() of struct push_backup_range to fetch the next range and to
acknowledge it, without going through dm messages on the data path. The
fd pins struct push_backup with a kref so it survives target removal and
simply returns -ENODEV afterwards. The legacy messages are kept for
compatibility.
Patches 1-4 are fixes found while working on this:
1. init the lock, waitqueue and timer before anything that can fail so
pb_destroy() is safe from any error path;
2. clear pb->alive under pb->lock like every other user does;
3. drop the redundant mod_timer() in push_backup_write(). The timer
re-arms itself from pb->deadline_jiffies, so updating the deadline
under the lock is enough. This was also the only place that armed
the timer outside the window push_backup_stop() waits for, which
matters once writes may arrive via the fd without pb->ctl_rwsem;
4. pass absolute expiry to mod_timer(). Both remaining callers passed
a relative value, so after ~5 min of uptime the timer fired and
re-armed on every tick while a write was delayed.
https://virtuozzo.atlassian.net/browse/VSTOR-152912
Andrey Zhadchenko (5):
drivers/md/push_backup: correct initialization
drivers/md/push_backup: clear pb->alive under pb->lock
drivers/md/push_backup: do not re-arm deadline timer in
push_backup_write()
drivers/md/push_backup: fix mod_timer() usage
dm/push_backup: add event file descriptor interface
drivers/md/dm-push-backup.c | 231 ++++++++++++++++++++++------
include/uapi/linux/dm-push-backup.h | 36 +++++
2 files changed, 220 insertions(+), 47 deletions(-)
create mode 100644 include/uapi/linux/dm-push-backup.h
--
2.43.5
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next reply other threads:[~2026-11-02 23:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 23:38 Andrey Zhadchenko [this message]
2026-11-02 23:38 ` [Devel] [PATCH hci-8.1 1/5] drivers/md/push_backup: correct initialization Andrey Zhadchenko
2026-11-02 23:46 ` no-reply
2026-11-02 23:38 ` [Devel] [PATCH hci-8.1 2/5] drivers/md/push_backup: clear pb->alive under pb->lock Andrey Zhadchenko
2026-11-02 23:47 ` no-reply
2026-11-02 23:38 ` [Devel] [PATCH hci-8.1 3/5] drivers/md/push_backup: do not re-arm deadline timer in push_backup_write() Andrey Zhadchenko
2026-11-02 23:48 ` no-reply
2026-11-02 23:38 ` [Devel] [PATCH hci-8.1 4/5] drivers/md/push_backup: fix mod_timer() usage Andrey Zhadchenko
2026-11-02 23:47 ` no-reply
2026-11-02 23:38 ` [Devel] [PATCH hci-8.1 5/5] dm/push_backup: add event file descriptor interface Andrey Zhadchenko
2026-11-02 23:51 ` no-reply
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=20261102233849.613155-1-andrey.zhadchenko@virtuozzo.com \
--to=andrey.zhadchenko@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.