From: Christian Ebner <c.ebner@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH v3 proxmox-backup] client: catalog shell: avoid navigating below archive root
Date: Tue, 3 Sep 2024 14:39:46 +0200 [thread overview]
Message-ID: <20240903123946.332720-1-c.ebner@proxmox.com> (raw)
Avoid to underflow the catalogs shell position stack by navigating
below the archives root directory into the catalog root. Otherwise
the shell will panic, as the root entry is always expected to be
present.
This threats the archive root directory as being it's own parent
directory, mimicking the behaviour of most common shells.
Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
---
Encountered while implementing the catalog shell for the split pxar
archive case.
Without this additional check, underflowing the pxar archive root of
the catalog shell will panic.
changes since version 2, thanks @Wolfgang for catching this:
- also handle cases where the current working directory is not the root
directory
changes since version 1:
- use `is_empty` to check if vector is empty
- extend commit message and comment to clarify that archive root acts as
its own parent directory
pbs-client/src/catalog_shell.rs | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/pbs-client/src/catalog_shell.rs b/pbs-client/src/catalog_shell.rs
index 349bb7cbc..f687e7e14 100644
--- a/pbs-client/src/catalog_shell.rs
+++ b/pbs-client/src/catalog_shell.rs
@@ -720,6 +720,14 @@ impl Shell {
&mut None,
)
.await?;
+
+ if new_position.is_empty() {
+ // Avoid moving below archive root into catalog root, thereby treating
+ // the archive root as its own parent directory.
+ self.position.truncate(1);
+ return Ok(());
+ }
+
if !new_position.last().unwrap().catalog.is_directory() {
bail!("not a directory");
}
--
2.39.2
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
reply other threads:[~2024-09-03 12:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240903123946.332720-1-c.ebner@proxmox.com \
--to=c.ebner@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