Re: [PATCH proxmox-backup v3 0/3] fix #6990: server: drop verify state on push & pull job

[Christian Ebner <c.ebner@proxmox.com>]

On 9/22/26 3:11 PM, Jakob Klocker wrote:
> When syncing a snapshot to another datastore, the source's verify_state
> is currently carried over to the target. This reports the target
> snapshot as verified even though its stored copy was never checked
> there. Since verify jobs skip snapshots that already carry a
> verify_state, the target's copy can't be verified again.
> 
> Chunks are checksummed in memory while being transferred, but a verify
> serves a different purpose: confirming the write to the (external)
> target actually succeeded.
> 
> This series stops the target from inheriting the source's
> verify_state, so the target is verified independently. On pull, a
> verify_state the target obtained on its own is preserved; on push the
> state is dropped unconditionally. It also moves the blocking calls in
> the touched code paths off the runtime's worker threads onto the
> blocking thread pool.
> 
> Tested (verify_state correctly stripped on target):
>   * Pull, verified source, new content, clean sync
>   * Pull, verified source, existing content, clean sync
>   * Pull, corrupted target, resync-corrupt
>   * Push, verified source (has no corrupt path)
>   * Pull, independently-verified target, clean re-sync - state preserved

Could not find any issues apart the mentioned comments and notes left on 
individual patches.

With those addressed, consider:

Reviewed-by: Christian Ebner <c.ebner@proxmox.com>
Tested-by: Christian Ebner <c.ebner@proxmox.com>