From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH qemu-server 0/2] fix #6882: backup provider api: fix backup with TPM state by correctly generating node name
Date: Fri, 3 Oct 2025 13:53:25 +0200 [thread overview]
Message-ID: <175949240126.1168105.17336943156910192790.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251003103319.44974-1-f.ebner@proxmox.com>
On Fri, 03 Oct 2025 12:33:09 +0200, Fiona Ebner wrote:
> The backup-access API in QEMU expects the '-backup' suffix to be
> present for the TPM state fleecing image too. This is a regression of
> the switch to using blockdev for fleecing images with commit f92c1fa0
> ("backup: use blockdev for fleecing images"). Add special handling to
> the fleecing_node_name() helper to fix it.
>
> Fleecing backups to native plugins do not use a dedicated image for
> the TPM state, so this only affected the backup provider API.
>
> [...]
Applied, thanks!
[1/2] fix #6882: backup provider api: fix backup with TPM state by correctly generating node name
commit: cd82e3f270d9310076da248c3f699c2a460d9628
[2/2] backup: fleecing: avoid warning when querying block node size for TPM state
commit: 33c0169fefe6a7d5a011c2539df59356674335e2
Best regards,
--
Fabian Grünbichler <f.gruenbichler@proxmox.com>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-10-03 11:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-03 10:33 [pve-devel] " Fiona Ebner
2025-10-03 10:33 ` [pve-devel] [PATCH qemu-server 1/2] " Fiona Ebner
2025-10-03 10:33 ` [pve-devel] [PATCH qemu-server 2/2] backup: fleecing: avoid warning when querying block node size for TPM state Fiona Ebner
2025-10-03 11:53 ` Fabian Grünbichler [this message]
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=175949240126.1168105.17336943156910192790.b4-ty@proxmox.com \
--to=f.gruenbichler@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pve-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.