public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup] fix #3526: correctly filter tasks with 'since' and 'until'
Date: Tue, 13 Jul 2021 15:47:23 +0200	[thread overview]
Message-ID: <20210713134723.1354225-1-d.csapak@proxmox.com> (raw)

The previous assumption was that the Tasks returned by the Iterator are
sorted by the starttime, but that is not actually the case, and
could never have been, since we append the tasks into the log when
they are finished (not started) and running tasks are always iterated
first.

So to correctly filter, we have to go through all tasks that could
fall into the correct time frame, possibly collecting some along the way
that we have to filter out again in the filter_map.

Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
 src/api2/node/tasks.rs | 26 +++++++++++++++++++++++++-
 1 file changed, 25 insertions(+), 1 deletion(-)

diff --git a/src/api2/node/tasks.rs b/src/api2/node/tasks.rs
index 34e71af1..3d3f7a0a 100644
--- a/src/api2/node/tasks.rs
+++ b/src/api2/node/tasks.rs
@@ -461,7 +461,15 @@ pub fn list_tasks(
         })
         .take_while(|info| {
             match (info, since) {
-                (Ok(info), Some(since)) => info.upid.starttime > since,
+                (Ok(info), Some(since)) => {
+                    // list is really sorted by endtime, so we have
+                    // to take until endtime is smaller than 'since'
+                    if let Some(ref state) = info.state {
+                        state.endtime() > since
+                    } else {
+                        true
+                    }
+                },
                 (Ok(_), None) => true,
                 (Err(_), _) => false,
             }
@@ -472,6 +480,22 @@ pub fn list_tasks(
             Err(_) => return None,
         };
 
+        // we have to filter here again for 'until', because there could have
+        // been some long running active task that could not have been skipped
+        if let Some(until) = until {
+            if info.upid.starttime > until {
+                return None;
+            }
+        }
+
+        // we have to filter again for 'since', because we have collected
+        // until both start and endtime were smaller than since
+        if let Some(since) = since {
+            if info.upid.starttime < since {
+                return None;
+            }
+        }
+
         if !list_all && check_task_access(&auth_id, &info.upid).is_err() {
             return None;
         }
-- 
2.30.2





             reply	other threads:[~2021-07-13 13:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-13 13:47 Dominik Csapak [this message]
2021-07-14  7:00 Dietmar Maurer

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=20210713134723.1354225-1-d.csapak@proxmox.com \
    --to=d.csapak@proxmox.com \
    --cc=pbs-devel@lists.proxmox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal