linux-kernel - Re: [PATCH resend] timers, sched_clock: Update timeout for clock wrap

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: <CALAqxLXEmXRyQ6VxgkroguEeu94z8YZgSQA-xaoHZeoWPJsFQg@mail.gmail.com>
Date:   Thu, 23 Mar 2017 12:38:55 -0700
From:   John Stultz <john.stultz@...aro.org>
To:     David Engraf <david.engraf@...go.com>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH resend] timers, sched_clock: Update timeout for clock wrap

On Thu, Mar 2, 2017 at 1:02 AM, David Engraf <david.engraf@...go.com> 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 <david.engraf@...go.com>

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

thanks
-john