]> Git Repo - qemu.git/commitdiff
fw_cfg: Allow reboot-timeout=-1 again
authorDr. David Alan Gilbert <[email protected]>
Fri, 25 Oct 2019 16:57:06 +0000 (17:57 +0100)
committerPhilippe Mathieu-Daudé <[email protected]>
Fri, 1 Nov 2019 18:19:24 +0000 (19:19 +0100)
Commit ee5d0f89de3e53cdb0dc added range checking on reboot-timeout
to only allow the range 0..65535; however both qemu and libvirt document
the special value -1  to mean don't reboot.
Allow it again.

Fixes: ee5d0f89de3e53cdb0dc ("fw_cfg: Fix -boot reboot-timeout error checking")
RH bz: https://bugzilla.redhat.com/show_bug.cgi?id=1765443
Signed-off-by: Dr. David Alan Gilbert <[email protected]>
Message-Id: <20191025165706[email protected]>
Suggested-by: Laszlo Ersek <[email protected]>
Message-Id: <37ac197c-f20e-dd05-ff6a-13a2171c7148@redhat.com>
[PMD: Applied Laszlo's suggestions]
Reviewed-by: Laszlo Ersek <[email protected]>
Signed-off-by: Philippe Mathieu-Daudé <[email protected]>
hw/nvram/fw_cfg.c

index aef1727250409d8fc19e27d3df93d33051a61cc4..14f843798392187f8a11b177bb652ec37337cad3 100644 (file)
@@ -237,7 +237,7 @@ static void fw_cfg_bootsplash(FWCfgState *s)
 static void fw_cfg_reboot(FWCfgState *s)
 {
     const char *reboot_timeout = NULL;
-    int64_t rt_val = -1;
+    uint64_t rt_val = -1;
     uint32_t rt_le32;
 
     /* get user configuration */
@@ -247,10 +247,11 @@ static void fw_cfg_reboot(FWCfgState *s)
 
     if (reboot_timeout) {
         rt_val = qemu_opt_get_number(opts, "reboot-timeout", -1);
+
         /* validate the input */
-        if (rt_val < 0 || rt_val > 0xffff) {
+        if (rt_val > 0xffff && rt_val != (uint64_t)-1) {
             error_report("reboot timeout is invalid,"
-                         "it should be a value between 0 and 65535");
+                         "it should be a value between -1 and 65535");
             exit(1);
         }
     }
This page took 0.030966 seconds and 4 git commands to generate.