public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Christian Ebner <c.ebner@proxmox.com>,
	Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH v2 stable-2 pxar 1/1] format/decoder/accessor: backport pxar entry type `Version`
Date: Thu, 06 Jun 2024 11:05:32 +0200	[thread overview]
Message-ID: <1717664701.1q0p407pbc.astroid@yuna.none> (raw)
In-Reply-To: <f3a788d6-f823-4ca3-ba50-a43c3d317273@proxmox.com>

On June 6, 2024 10:49 am, Christian Ebner wrote:
> On 6/6/24 10:21, Fabian Grünbichler wrote:
>> On June 5, 2024 5:41 pm, Christian Ebner wrote:
>>> Backports the pxar format entry type `Version` and the associated
>>> decoder methods. The format version entry is expected once as the
>>> first entry of the pxar archive, marked with a `PXAR_FORMAT_VERSION`
>>> header followed by the encoded version number for archives with
>>> format version 2 or higher.
>>> If not present, the default format version 1 is assumed as encoding
>>> format for the archive.
>>>
>>> The entry allows to early detect and bail if an incompatible archive
>>> version is encountered.
>>>
>>> The format version entry is not backwards compatible to pxar format
>>> version 1.
>>>
>>> Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
>> 
>>>       /// Symbolic links.
>>>       Symlink(format::Symlink),
>>>   
>>> diff --git a/tests/simple/fs.rs b/tests/simple/fs.rs
>>> index 9a89c4d..fd13e65 100644
>>> --- a/tests/simple/fs.rs
>>> +++ b/tests/simple/fs.rs
>>> @@ -229,6 +229,7 @@ impl Entry {
>>>                       })?))
>>>                   };
>>>               match item.kind() {
>>> +                PxarEntryKind::Version(_) => continue,
>> 
>> and as a result, this?
> 
> Same, given that I think this would not even require the patches on the 
> pbs side anymore, as the decoder/accessor will always fail anyway.

that was my conclusion as well (still needs a stable-2 rebuild with the
bumped stable-2 pxar of course).


_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel

  reply	other threads:[~2024-06-06  9:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 15:41 [pbs-devel] [PATCH v2 stable-2 pxar proxmox-backup 0/2] backport pxar format version check Christian Ebner
2024-06-05 15:41 ` [pbs-devel] [PATCH v2 stable-2 pxar 1/1] format/decoder/accessor: backport pxar entry type `Version` Christian Ebner
2024-06-06  8:21   ` Fabian Grünbichler
2024-06-06  8:49     ` Christian Ebner
2024-06-06  9:05       ` Fabian Grünbichler [this message]
2024-06-05 15:41 ` [pbs-devel] [PATCH v2 stable-2 proxmox-backup 2/2] client: pxar: bail on incompatible format versions Christian Ebner

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=1717664701.1q0p407pbc.astroid@yuna.none \
    --to=f.gruenbichler@proxmox.com \
    --cc=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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal