public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
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 v2 qemu 4/4] vma: create: register all streams before entering coroutines
Date: Mon, 14 Feb 2022 15:51:57 +0100	[thread overview]
Message-ID: <735f0b1a-7173-f123-68ce-4c22fe887417@proxmox.com> (raw)
In-Reply-To: <20220214110257.160945-1-f.ebner@proxmox.com>

On 14.02.22 12:02, Fabian Ebner wrote:
> Otherwise, the header might already get written by a coroutine and
> registering further streams will fail after that.
> 
> Also adds a missing g_list_free call for the other GList that's used.

just as note:
it's cleaner this way, especially if we'd reuse `create_archive` in the future,
but currently this doesn't changes much, as it was the program exited immediately
afterwards, so returning all resources back to the OS, anyway.

> 
> Reported in the community forum:
> https://forum.proxmox.com/threads/104744/
> 
> Reproducer script (increase beyond 30 if the issue isn't triggered yet):
>> #!/usr/bin/perl
>>
>> my $dir = "./vma-create-bug";
>> mkdir $dir;
>>
>> my $archive_path = "$dir/vzdump-qemu-104-2202_02_02-00_00_00.vma";
>> unlink $archive_path;
>>
>> my $cmd = "vma create $archive_path -v";
>> for (my $i = 0; $i < 30; $i++) {
>>   system("truncate -s 1M $dir/drive-virtio$i.img");
>>   $cmd .= " drive-virtio$i=$dir/drive-virtio$i.img";
>> }
>> system($cmd);
> 
> Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
> ---
> 
> A late addition to v2.

Also later unrelated, so I applied it now already, avoiding the need to release
6.2 to repos already for the forum user to test this.

> 
>  ...VE-Backup-add-vma-backup-format-code.patch | 24 +++++++++++++++----
>  1 file changed, 19 insertions(+), 5 deletions(-)
> 
>

applied, thanks!




  reply	other threads:[~2022-02-14 14:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11  9:24 [pve-devel] [PATCH v2 qemu 1/3] update submodule and patches to 6.2.0 Fabian Ebner
2022-02-11  9:24 ` [pve-devel] [PATCH v2 qemu 2/3] fix getopt-string when introducing -n option for qemu-img dd Fabian Ebner
2022-02-11  9:24 ` [pve-devel] [PATCH v2 qemu 3/3] add patch for loading a snapshot with " Fabian Ebner
2022-02-14 11:02 ` [pve-devel] [PATCH v2 qemu 4/4] vma: create: register all streams before entering coroutines Fabian Ebner
2022-02-14 14:51   ` Thomas Lamprecht [this message]
2022-02-15 15:08 ` [pve-devel] applied-series: [PATCH v2 qemu 1/3] update submodule and patches to 6.2.0 Thomas Lamprecht

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=735f0b1a-7173-f123-68ce-4c22fe887417@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal