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] [day] [month] [year] [list]
Date:   Thu, 23 Mar 2017 12:38:55 -0700
From:   John Stultz <>
To:     David Engraf <>
Cc:     Thomas Gleixner <>,
        lkml <>
Subject: Re: [PATCH resend] timers, sched_clock: Update timeout for clock wrap

On Thu, Mar 2, 2017 at 1:02 AM, David Engraf <> wrote:
> The scheduler clock framework may not use the correct timeout for the clock
> wrap. This happens when a new clock driver calls sched_clock_register()
> after the kernel called sched_clock_postinit(). In this case the clock wrap
> timeout is too long thus sched_clock_poll() is called too late and the clock
> already wrapped.
> On my ARM system the scheduler was no longer scheduling any other task than
> the idle task because the sched_clock() wrapped.
> Signed-off-by: David Engraf <>

Thanks for sending this in! It looks sane, so I've queued it.


Powered by blists - more mailing lists