From: Christian Ebner <c.ebner@proxmox.com>
To: Jakob Klocker <j.klocker@proxmox.com>, pbs-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox-backup v2 2/3] fix #6990: server: drop verify state on push job
Date: Fri, 28 Aug 2026 12:30:50 +0200 [thread overview]
Message-ID: <de9cba3c-ed93-4219-90a3-3801a453ca26@proxmox.com> (raw)
In-Reply-To: <20260821111826.299588-3-j.klocker@proxmox.com>
On 8/21/26 1:18 PM, Jakob Klocker wrote:
> When pushing a snapshot the target manifest is recreated from the source
> manifest, copying its verify_state. As with pull, this makes the pushed
> snapshot appear verified on the remote without its stored copy having
> been checked there.
> Strip verify_state after copying the unprotected section so the pushed
> snapshot is verified independently on the target.
>
> Link: https://bugzilla.proxmox.com/show_bug.cgi?id=6990
> Signed-off-by: Jakob Klocker <j.klocker@proxmox.com>
> ---
Reviewed-by: Christian Ebner <c.ebner@proxmox.com>
next prev parent reply other threads:[~2026-08-28 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 11:18 [PATCH proxmox-backup v2 0/3] fix #6990: server: drop verify state on push & pull job Jakob Klocker
2026-08-21 11:18 ` [PATCH proxmox-backup v2 1/3] server: pull: run blocking file operations on the blocking pool Jakob Klocker
2026-08-28 10:30 ` Christian Ebner
2026-08-21 11:18 ` [PATCH proxmox-backup v2 2/3] fix #6990: server: drop verify state on push job Jakob Klocker
2026-08-28 10:30 ` Christian Ebner [this message]
2026-08-21 11:18 ` [PATCH proxmox-backup v2 3/3] fix #6990: server: drop verify state on non-decrypt pull job Jakob Klocker
2026-08-28 11:11 ` 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=de9cba3c-ed93-4219-90a3-3801a453ca26@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=j.klocker@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 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.