Martin Stein 3f37a12e2d timer connection: fix mixing of time sources ... We update the alarm-scheduler time with results of Timer::Connection::curr_time when we schedule new timeouts but when handling the signal from the Timer server we updated the alarm-scheduler time with the result of Timer::Connection::elapsed_us. Mixing times like this could cause a non-monotone time value in the alarm scheduler. The alarm scheduler then thought that the time value wrapped and triggered all timeouts immediately. The problem was fixed by always using Timer::Connection::curr_time as time source. Ref #2490		2017-10-05 17:40:02 +02:00
..
alarm	alarm: fix information loss due to int-cast	2017-10-05 17:39:56 +02:00
blit	Adjust file headers to refer to the AGPLv3	2017-02-28 12:59:29 +01:00
net	Adjust file headers to refer to the AGPLv3	2017-02-28 12:59:29 +01:00
server	base: classify signals as I/O and application level	2017-05-31 13:15:58 +02:00
timed_semaphore	timed_semaphore: fix deprecated warning	2017-05-31 13:16:19 +02:00
timeout	timer connection: fix mixing of time sources	2017-10-05 17:40:02 +02:00
trace/policy	Adjust file headers to refer to the AGPLv3	2017-02-28 12:59:29 +01:00
vfs	VFS: nonblocking interface	2017-08-28 16:49:38 +02:00