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: <20170823133535.0b53f6d5@canb.auug.org.au>
Date:   Wed, 23 Aug 2017 13:35:35 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     jeffy <jeffy.chen@...k-chips.com>
Cc:     Nicholas Piggin <npiggin@...il.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        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, 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 jeffy,

On Wed, 23 Aug 2017 11:21:40 +0800 jeffy <jeffy.chen@...k-chips.com> wrote:
>
> 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)

I had the same problem with a powerpc le qemu boot.  Paul has now
removed v1 from his rcu tree, so it will not be in linux-next today.

-- 
Cheers,
Stephen Rothwell