From 3d0386f27ca66379acf50199e1d1298386eeeeb8 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Mon, 6 May 2024 02:55:53 +0200 Subject: Adding upstream version 3.2.1. Signed-off-by: Daniel Baumann --- modules/detect_time_jump/README.rst | 20 ++++++++++++ modules/detect_time_jump/detect_time_jump.lua | 44 +++++++++++++++++++++++++++ modules/detect_time_jump/detect_time_jump.mk | 2 ++ 3 files changed, 66 insertions(+) create mode 100644 modules/detect_time_jump/README.rst create mode 100644 modules/detect_time_jump/detect_time_jump.lua create mode 100644 modules/detect_time_jump/detect_time_jump.mk (limited to 'modules/detect_time_jump') diff --git a/modules/detect_time_jump/README.rst b/modules/detect_time_jump/README.rst new file mode 100644 index 0000000..240907f --- /dev/null +++ b/modules/detect_time_jump/README.rst @@ -0,0 +1,20 @@ +.. _mod-detect_time_jump: + +Detect discontinuous jumps in the system time +--------------------------------------------- + +This module detect discontinuous jumps in the system time when resolver +is running. It clears cache when a significant backward time jumps occurs. + +Time jumps are usually created by NTP time change or by admin intervention. +These change can affect cache records as they store timestamp and TTL in real +time. + +If you want to preserve cache during time travel you should disable +this module by ``modules.unload('detect_time_jump')``. + +Due to the way monotonic system time works on typical systems, +suspend-resume cycles will be perceived as forward time jumps, +but this direction of shift does not have the risk of using records +beyond their intended TTL, so forward jumps do not cause erasing the cache. + diff --git a/modules/detect_time_jump/detect_time_jump.lua b/modules/detect_time_jump/detect_time_jump.lua new file mode 100644 index 0000000..65ae060 --- /dev/null +++ b/modules/detect_time_jump/detect_time_jump.lua @@ -0,0 +1,44 @@ +-- Module interface +local ffi = require('ffi') + +local mod = {} +mod.threshold = 10 * min +local event_id = nil + +-- Get time of last cache clear. Compute difference between realtime +-- and monotonic time. Compute difference of actual realtime and monotonic +-- time. In ideal case these differences should be almost same. +-- If they differ more than mod.threshold value then clear cache. +local function check_time() + local checkpoint = cache.checkpoint() + local cache_timeshift = checkpoint.walltime.sec * 1000 - checkpoint.monotime + local actual_timeshift = os.time() * 1000 - tonumber(ffi.C.kr_now()) + local jump_backward = cache_timeshift - actual_timeshift + if jump_backward > mod.threshold then + log("Detected backwards time jump, clearing cache.\n" .. + "But what does that mean? It means your future hasn't been written yet." + ) + cache.clear() + elseif -jump_backward > mod.threshold then + -- On Linux 4.17+ this shouldn't happen anymore: https://lwn.net/Articles/751482/ + log("Detected forward time jump. (Suspend-resume, possibly.)") + cache.checkpoint(true) + end +end + +function mod.init() + if event_id then + error("Module is already loaded.") + else + event_id = event.recurrent(1 * min , check_time) + end +end + +function mod.deinit() + if event_id then + event.cancel(event_id) + event_id = nil + end +end + +return mod diff --git a/modules/detect_time_jump/detect_time_jump.mk b/modules/detect_time_jump/detect_time_jump.mk new file mode 100644 index 0000000..04df607 --- /dev/null +++ b/modules/detect_time_jump/detect_time_jump.mk @@ -0,0 +1,2 @@ +detect_time_jump_SOURCES := detect_time_jump.lua +$(call make_lua_module,detect_time_jump) -- cgit v1.2.3