From: Andrey Zhadchenko <andrey.zhadchenko@virtuozzo.com>
To: alexander.ivanov@virtuozzo.com
Cc: devel@openvz.org
Subject: [Devel] [PATCH hci-8.1 v2 5/6] drivers/md/push_backup: arm deadline timer under pb->lock
Date: Tue, 3 Nov 2026 03:32:45 +0300 [thread overview]
Message-ID: <20261103003246.712239-6-andrey.zhadchenko@virtuozzo.com> (raw)
In-Reply-To: <20261103003246.712239-1-andrey.zhadchenko@virtuozzo.com>
When push_backup_write acks last delayed request it sets
deadline_jiffies = S64_MAX and the next fired timer uses this
for mod_timer(): expiry is not set to some very distant future.
Previously a later push_backup_write() would accidentally
repair the expiry; since it no longer touches the timer, nothing
does until stop.
Make the decision and the arming atomic: call mod_timer() under
pb->lock at both sites, and do not re-arm when nothing is delayed.
mod_timer() and queue_work() are fine under a spinlock, and the timer
base lock is dropped while the callback runs, so there is no lock
inversion.
As a bonus the rcu_read_lock()/synchronize_rcu() dance between
postpone_if_required_for_backup() and push_backup_stop() is no longer
needed: cleanup_backup() clears pb->alive under pb->lock, the timer is
only armed under pb->lock while pb->alive is set, and the callback
re-arming itself is handled by timer_delete_sync_try(). Drop it.
https://virtuozzo.atlassian.net/browse/VSTOR-152912
Signed-off-by: Andrey Zhadchenko <andrey.zhadchenko@virtuozzo.com>
---
v2: new patch
drivers/md/dm-push-backup.c | 20 ++++++++------------
1 file changed, 8 insertions(+), 12 deletions(-)
diff --git a/drivers/md/dm-push-backup.c b/drivers/md/dm-push-backup.c
index b1861204f6e3e..8f2015e8e29a4 100644
--- a/drivers/md/dm-push-backup.c
+++ b/drivers/md/dm-push-backup.c
@@ -241,23 +241,24 @@ static void pb_timer_func(struct timer_list *timer)
spin_lock_irqsave(&pb->lock, flags);
deadline = pb->deadline_jiffies;
- spin_unlock_irqrestore(&pb->lock, flags);
-
+ if (deadline == S64_MAX)
+ goto unlock; /* Nothing is delayed, let the timer idle */
if (unlikely(time_before64(now, deadline)))
mod_timer(timer, jiffies + (deadline - now) + 1);
else
queue_work(pb->wq, &pb->worker);
+unlock:
+ spin_unlock_irqrestore(&pb->lock, flags);
}
static int postpone_if_required_for_backup(struct push_backup *pb,
struct request *rq)
{
- bool queue_timer = false;
struct pb_bio *pbio;
unsigned long flags;
+ bool wake = false;
int ret = 0;
- rcu_read_lock(); /* See push_backup_stop() */
spin_lock_irqsave(&pb->lock, flags);
if (!pb->alive)
goto unlock;
@@ -272,16 +273,13 @@ static int postpone_if_required_for_backup(struct push_backup *pb,
pb->nr_delayed += 1;
if (pb->nr_delayed == 1) {
pb->deadline_jiffies = get_jiffies_64() + pb->timeout_in_jiffies;
- queue_timer = true;
+ mod_timer(&pb->deadline_timer, jiffies + pb->timeout_in_jiffies + 1);
+ wake = true;
}
unlock:
spin_unlock_irqrestore(&pb->lock, flags);
- if (queue_timer)
- mod_timer(&pb->deadline_timer, jiffies + pb->timeout_in_jiffies + 1);
- rcu_read_unlock();
-
- if (queue_timer)
+ if (wake)
wake_up_interruptible(&pb->waitq);
return ret;
@@ -400,8 +398,6 @@ static int push_backup_stop(struct push_backup *pb,
return -EBADF;
cleanup_backup(pb);
- /* Wait postpone_if_required_for_backup() starts timer */
- synchronize_rcu();
WARN_ON_ONCE(timer_delete_sync_try(&pb->deadline_timer) < 0);
flush_workqueue(pb->wq);
--
2.43.5
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next prev parent reply other threads:[~2026-11-03 0:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 0:32 [Devel] [PATCH hci-8.1 v2 0/6] dm/push_backup: event fd interface and fixes Andrey Zhadchenko
2026-11-03 0:32 ` [Devel] [PATCH hci-8.1 v2 1/6] drivers/md/push_backup: correct initialization Andrey Zhadchenko
2026-11-03 0:40 ` no-reply
2026-11-03 0:32 ` [Devel] [PATCH hci-8.1 v2 2/6] drivers/md/push_backup: clear pb->alive under pb->lock Andrey Zhadchenko
2026-11-03 0:39 ` no-reply
2026-11-03 0:32 ` [Devel] [PATCH hci-8.1 v2 3/6] drivers/md/push_backup: do not re-arm deadline timer in push_backup_write() Andrey Zhadchenko
2026-11-03 0:41 ` no-reply
2026-11-03 0:32 ` [Devel] [PATCH hci-8.1 v2 4/6] drivers/md/push_backup: fix mod_timer() usage Andrey Zhadchenko
2026-11-03 0:41 ` no-reply
2026-11-03 0:32 ` Andrey Zhadchenko [this message]
2026-11-03 0:45 ` [Devel] [PATCH hci-8.1 v2 5/6] drivers/md/push_backup: arm deadline timer under pb->lock no-reply
2026-11-03 0:32 ` [Devel] [PATCH hci-8.1 v2 6/6] dm/push_backup: add event file descriptor interface Andrey Zhadchenko
2026-11-03 0:46 ` 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=20261103003246.712239-6-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox