From: Paul Durrant <paul.durrant@citrix.com>
Date: Mon, 8 May 2017 15:58:43 +0000 (+0100)
Subject: Reboot request keys should be volatile
X-Git-Tag: 8.2.1~3
X-Git-Url: http://xenbits.xensource.com/gitweb?a=commitdiff_plain;h=ff7f011f65ad7cdbcbc653eb58b791842905f450;p=pvdrivers%2Fwin%2Fxenbus.git

Reboot request keys should be volatile

When a driver makes a reboot request it should use a volatile registry key.
The monitor service will explicitly remove the key prior to reboot but,
if the reboot is initiated in some other way and the key is non-volatile,
the monitor service will then needlessly prompt for a second reboot.

Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
---

diff --git a/src/xenbus/driver.c b/src/xenbus/driver.c
index e9cb6f4..bbbda6c 100644
--- a/src/xenbus/driver.c
+++ b/src/xenbus/driver.c
@@ -161,7 +161,7 @@ __DriverRequestReboot(
 
     status = RegistryCreateSubKey(RequestKey,
                                   __MODULE__,
-                                  REG_OPTION_NON_VOLATILE,
+                                  REG_OPTION_VOLATILE,
                                   &SubKey);
     if (!NT_SUCCESS(status))
         goto fail3;