linux-kernel - Re: [PATCH] clocksource: Use same threshold for read-back delay and time skew

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <875x8z2ris.ffs@tglx>
Date: Sun, 18 Jan 2026 10:34:35 +0100
From: Thomas Gleixner <tglx@...nel.org>
To: Waiman Long <llong@...hat.com>, Jiri Wiesner <jwiesner@...e.de>, Linux
 Kernel Mailing List <linux-kernel@...r.kernel.org>
Cc: "Paul E. McKenney" <paulmck@...nel.org>, Feng Tang
 <feng.tang@...el.com>, John Stultz <jstultz@...gle.com>, Stephen Boyd
 <sboyd@...nel.org>
Subject: Re: [PATCH] clocksource: Use same threshold for read-back delay and
 time skew

On Fri, Jan 16 2026 at 15:05, Waiman Long wrote:
> On 1/16/26 1:08 PM, Jiri Wiesner wrote:
> I think wd_seq_delay should compare to just one 
> watchdog->uncertainty_margin. See my comment on a related patch sent out 
> by Thomas.
>
> https://lore.kernel.org/lkml/8178bbf3-4a9d-4add-93bb-2ebd4dc03e9f@redhat.com/

Duh. I completely forgot about that one....