From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fabian Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH-SERIES v2 qemu] vma/alloc-track improvements
Date: Wed, 22 Jun 2022 17:31:26 +0200 [thread overview]
Message-ID: <bf337583-8c66-3b96-942a-675cac84f677@proxmox.com> (raw)
In-Reply-To: <20220622084513.160867-1-f.ebner@proxmox.com>
Am 22/06/2022 um 10:45 schrieb Fabian Ebner:
> Most important is the first patch, as it fixes backing up templates
> with efitype=4m EFI disk on file storages (or other 64-KiB-unaligned
> disk) to non-PBS. Also reported in the community forum, most recently:
> https://forum.proxmox.com/threads/104740/post-479298
>
> Second vma-related patch is to be more graceful in error scenario upon
> creation. alloc-track patch is to avoid a bogus break, but might even
> be dead code in practice.
>
> vma-related patches can be squashed into
> 0026-PVE-Backup-add-vma-backup-format-code.patch
>
> alloca-track patch can be squashed into
> 0047-block-add-alloc-track-driver.patch
>
> Fabian Ebner (3):
> vma: create: support 64KiB-unaligned input images
> vma: create: avoid triggering assertion in error case
> block: alloc-track: avoid premature break
>
> block/alloc-track.c | 3 ++-
> vma-writer.c | 2 ++
> vma.c | 12 ++++++++++--
> 3 files changed, 14 insertions(+), 3 deletions(-)
>
applied, thanks!
prev parent reply other threads:[~2022-06-22 15:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 8:45 [pve-devel] " Fabian Ebner
2022-06-22 8:45 ` [pve-devel] [PATCH v2 qemu 1/3] vma: create: support 64KiB-unaligned input images Fabian Ebner
2022-06-22 8:45 ` [pve-devel] [PATCH v2 qemu 2/3] vma: create: avoid triggering assertion in error case Fabian Ebner
2022-06-22 8:45 ` [pve-devel] [PATCH v2 qemu 3/3] block: alloc-track: avoid premature break Fabian Ebner
2022-06-22 15:31 ` Thomas Lamprecht [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=bf337583-8c66-3b96-942a-675cac84f677@proxmox.com \
--to=t.lamprecht@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox