]> git.ipfire.org Git - thirdparty/kernel/linux.git/commit
clocksource: Don't use non-continuous clocksources as watchdog
authorThomas Gleixner <tglx@kernel.org>
Fri, 23 Jan 2026 23:17:57 +0000 (00:17 +0100)
committerThomas Gleixner <tglx@kernel.org>
Thu, 12 Mar 2026 11:23:27 +0000 (12:23 +0100)
commit1432f9d4e8aa2d7585b678bdd0b740597af00d6e
treea1fc7285883f8c7dc55a5f78b27698228d71adbd
parent79ccb0693a99e1b91eba95c6bd32a3e02be156ae
clocksource: Don't use non-continuous clocksources as watchdog

Using a non-continuous aka untrusted clocksource as a watchdog for another
untrusted clocksource is equivalent to putting the fox in charge of the
henhouse.

That's especially true with the jiffies clocksource which depends on
interrupt delivery based on a periodic timer. Neither the frequency of that
timer is trustworthy nor the kernel's ability to react on it in a timely
manner and rearm it if it is not self rearming.

Just don't bother to deal with this. It's not worth the trouble and only
relevant to museum piece hardware.

Signed-off-by: Thomas Gleixner <tglx@kernel.org>
Link: https://patch.msgid.link/20260123231521.858743259@kernel.org
kernel/time/clocksource.c