diff options
author | 2024-12-17 21:49:06 +0100 | |
---|---|---|
committer | 2025-01-10 13:50:00 +0100 | |
commit | 579e7fd383ff3f7a4f685489f8fe18cfd8659074 (patch) | |
tree | feef61e31fb2de558cd7eb0427f20efacd31652e /scripts/generate_rust_analyzer.py | |
parent | um: Remove unused user_context function (diff) | |
download | wireguard-linux-579e7fd383ff3f7a4f685489f8fe18cfd8659074.tar.xz wireguard-linux-579e7fd383ff3f7a4f685489f8fe18cfd8659074.zip |
um: rtc: use RTC time when calculating the alarm
The kernel realtime and the current RTC time may have a (small) offset.
Should the kernel time be slightly in the future, then the timeout is
zero. This is problematic in time-travel mode, as a zero timeout can be
correctly configured and time never advances.
Replace the kernel realtime read with a read of the actual persistent
RTC clock. Also, for time-travel, calculate the exact nanoseconds needed
for the clock to advance.
Signed-off-by: Benjamin Berg <benjamin.berg@intel.com>
Co-developed-by: Avraham Stern <avraham.stern@intel.com>
Link: https://patch.msgid.link/20241217204906.1408011-1-benjamin@sipsolutions.net
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions