public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fabian Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH/RFC v2 qemu-server 3/3] restore_vma_archive: remove timeout for reading the device map
Date: Wed, 12 Aug 2020 12:01:27 +0200	[thread overview]
Message-ID: <20200812100127.29722-3-f.ebner@proxmox.com> (raw)
In-Reply-To: <20200812100127.29722-1-f.ebner@proxmox.com>

If there is no serious problem, it shouldn't be possible to run into
this timeout anyways. It's just (extracting and) reading the header of
the (compressed) vma file. And if there is a serious problem, then the
commands will most likely fail for a different reason, e.g. unable to open,
corrupt vma, etc.

Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
---

New in v2

Hope I'm not missing anything important.

 PVE/QemuServer.pm | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
index 794819b..342114d 100644
--- a/PVE/QemuServer.pm
+++ b/PVE/QemuServer.pm
@@ -6162,8 +6162,6 @@ sub restore_vma_archive {
 
     $add_pipe->(['vma', 'extract', '-v', '-r', $mapfifo, $readfrom, $tmpdir]);
 
-    my $timeout = 5;
-
     my $devinfo = {};
 
     my $rpcenv = PVE::RPCEnvironment::get();
@@ -6260,9 +6258,6 @@ sub restore_vma_archive {
 	    local $SIG{QUIT} =
 	    local $SIG{HUP} =
 	    local $SIG{PIPE} = sub { die "interrupted by signal\n"; };
-	local $SIG{ALRM} = sub { die "got timeout reading device map\n"; };
-
-	alarm($timeout);
 
 	my $parser = sub {
 	    my $line = shift;
@@ -6273,7 +6268,6 @@ sub restore_vma_archive {
 		my ($dev_id, $size, $devname) = ($1, $2, $3);
 		$devinfo->{$devname} = { size => $size, dev_id => $dev_id };
 	    } elsif ($line =~ m/^CTIME: /) {
-		alarm(0);
 		&$print_devmap();
 		print $fifofh "done\n";
 		close($fifofh);
@@ -6285,8 +6279,6 @@ sub restore_vma_archive {
     };
     my $err = $@;
 
-    alarm(0);
-
     $restore_deactivate_volumes->($cfg, $devinfo);
 
     unlink $mapfifo;
-- 
2.20.1





  parent reply	other threads:[~2020-08-12 10:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-12 10:01 [pve-devel] [PATCH v2 qemu-server 1/3] Fix #2816: remove timeout for allocation on restore Fabian Ebner
2020-08-12 10:01 ` [pve-devel] [PATCH/RFC v2 qemu-server 2/3] restore_vma_archive: get rid of oldtimeout handling Fabian Ebner
2020-08-20  8:55   ` Thomas Lamprecht
2020-08-12 10:01 ` Fabian Ebner [this message]
2020-08-20  8:53   ` [pve-devel] [PATCH/RFC v2 qemu-server 3/3] restore_vma_archive: remove timeout for reading the device map Thomas Lamprecht
2020-08-20  9:22     ` Fabian Ebner
2020-08-20  8:56 ` [pve-devel] [PATCH v2 qemu-server 1/3] Fix #2816: remove timeout for allocation on restore Thomas Lamprecht
2020-08-20  9:21   ` Fabian 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=20200812100127.29722-3-f.ebner@proxmox.com \
    --to=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