Update currentTime in dispatch loop

commit 312910b4e34215aaa50fc0c6092684d5878dc32f Author: Chase Douglas <chase.douglas@canonical.com> Date: Wed Apr 18 11:15:40 2012 -0700 Update currentTime in dispatch loop A request, like input device grabs, may check a request timestamp against currentTime. It is possible for currentTime to lag a previously sent event timestamp. If the client makes a request based on such an event timestamp, the request may fail the validity check against currentTime unless we always update the time before processing the request. Signed-off-by: Chase Douglas <chase.douglas@canonical.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>

Update currentTime in dispatch loop
7a2836f8 · Ulrich Sibiller · Mike Gabriel · 2589a134 · 7a2836f8
Commit 7a2836f8 authored Jul 02, 2019 by Ulrich Sibiller Committed by Mike Gabriel Sep 29, 2019
Show whitespace changes
Inline Side-by-side

Showing with 3 additions and 0 deletions

dispatch.c nx-X11/programs/Xserver/dix/dispatch.c +3 -0

No files found.
--- a/nx-X11/programs/Xserver/dix/dispatch.c
+++ b/nx-X11/programs/Xserver/dix/dispatch.c
@@ -407,6 +407,9 @@ Dispatch(void)
 		}
 		/* now, finally, deal with client requests */

+		/* Update currentTime so request time checks, such as for input
+		 * device grabs, are calculated correctly */
+		UpdateCurrentTimeIf();
 	        result = ReadRequestFromClient(client);
 	        if (result <= 0) 
 	        {