[win-pv-devel] [PATCH] Reboot request keys should be volatile

[Paul Durrant <paul.durrant@xxxxxxxxxx>]

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@xxxxxxxxxx>
---
 src/xenvif/driver.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/xenvif/driver.c b/src/xenvif/driver.c
index 43a9c7b..8bc097a 100644
--- a/src/xenvif/driver.c
+++ b/src/xenvif/driver.c
@@ -206,7 +206,7 @@ __DriverRequestReboot(
 
     status = RegistryCreateSubKey(RequestKey,
                                   __MODULE__,
-                                  REG_OPTION_NON_VOLATILE,
+                                  REG_OPTION_VOLATILE,
                                   &SubKey);
     if (!NT_SUCCESS(status))
         goto fail3;
-- 
2.5.3


_______________________________________________
win-pv-devel mailing list
win-pv-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/cgi-bin/mailman/listinfo/win-pv-devel