linux-kernel - Re: WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:245 initialize_tlbstate_and

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: <35089dad-d823-6cca-387c-f937b5ca5f16@kernel.dk>
Date:   Wed, 13 Sep 2017 10:28:27 -0600
From:   Jens Axboe <axboe@...nel.dk>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Andy Lutomirski <luto@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:245
 initialize_tlbstate_and_flush+0x6a/0x100

On 09/13/2017 10:26 AM, Linus Torvalds wrote:
> On Wed, Sep 13, 2017 at 9:11 AM, Jens Axboe <axboe@...nel.dk> wrote:
>>
>> I get this new warning when I suspend/resume my gen4 x1 laptop running
>> current -git. Looks like this commit is the problematic one:
> 
> Yes, ths fix should be percolating up from the x86 tip tree later
> today, I'm hoping. In the meantime, things should work with current
> -git (as long as you don't hibernate), apart from the ugly warning.

Great, sounds good. Things work fine, just noticed that I get a lot
of spew from that.

-- 
Jens Axboe