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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 7 Dec 2007 16:29:30 +1100
From:	Nick Piggin <>
To:	Stefano Brivio <>
Cc:	Ingo Molnar <>, Robert Love <>,, Dave Jones <>,
	"Rafael J. Wysocki" <>, Michael Buesch <>,
	Thomas Gleixner <>,
	Andrew Morton <>,
	Len Brown <>
Subject: Re: [PATCH] scheduler: fix x86 regression in native_sched_clock

On Friday 07 December 2007 12:19, Stefano Brivio wrote:
> This patch fixes a regression introduced by:
> commit bb29ab26863c022743143f27956cc0ca362f258c
> Author: Ingo Molnar <>
> Date:   Mon Jul 9 18:51:59 2007 +0200
> This caused the jiffies counter to leap back and forth on cpufreq changes
> on my x86 box. I'd say that we can't always assume that TSC does "small
> errors" only, when marked unstable. On cpufreq changes these errors can be
> huge.
> The original bug report can be found here:
> Signed-off-by: Stefano Brivio <>

While your fix should probably go into 2.6.24...

This particular issue has aggravated me enough times. Let's
fix the damn thing properly already... I think what would work best
is a relatively simple change to the API along these lines:

View attachment "sched-clock.patch" of type "text/x-diff" (7825 bytes)

Powered by blists - more mailing lists