linux-kernel - Re: [v2] timers: Fix excessive granularity of new timers after a nohz idle

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <599D2EC3.2010900@rock-chips.com>
Date:   Wed, 23 Aug 2017 15:29:07 +0800
From:   jeffy <jeffy.chen@...k-chips.com>
To:     Thomas Gleixner <tglx@...utronix.de>
CC:     Nicholas Piggin <npiggin@...il.com>, akpm@...ux-foundation.org,
        John Stultz <john.stultz@...aro.org>,
        Stephen Boyd <sboyd@...eaurora.org>,
        Jonathan.Cameron@...wei.com, paulmck@...ux.vnet.ibm.com,
        mpe@...erman.id.au, dzickus@...hat.com, sfr@...b.auug.org.au,
        linuxarm@...wei.com, abdhalee@...ux.vnet.ibm.com,
        linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org
Subject: Re: [v2] timers: Fix excessive granularity of new timers after a
 nohz idle

Hi Thomas,

On 08/23/2017 03:01 PM, Thomas Gleixner wrote:
> On Wed, 23 Aug 2017, jeffy wrote:
>
>> Hi guys,
>>
>> I was testing a arm64 based device(chromebook bob), and the kernel hang a
>> lot(during booting or suspending) on for-next(next-20170822) with this commit:
>> 71acb768f5b3 (timers: Fix excessive granularity of new timers after a nohz
>> idle)
>>
>> After revert it(or just add "!base->is_idle" check back), things work well...
>
> Can you please test V2?
>
hmm, v2 works...

Tested-by: Jeffy Chen <jeffy.chen@...k-chips.com>

> Thanks,
>
> 	tglx
>
>
>