linux-kernel - Re: [x86/mm/kaiser] a6c70b8b30: WARNING:at_kernel/locking/lockdep.c:#trace_hardirqs_off

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]

Date:   Sat, 25 Nov 2017 10:17:15 +0800
From:   Fengguang Wu <fengguang.wu@...el.com>
To:     Ingo Molnar <mingo@...nel.org>
Cc:     Dave Hansen <dave.hansen@...ux.intel.com>,
        Andy Lutomirski <luto@...nel.org>,
        Borislav Petkov <bp@...en8.de>,
        Brian Gerst <brgerst@...il.com>,
        Daniel Gruss <daniel.gruss@...k.tugraz.at>,
        Denys Vlasenko <dvlasenk@...hat.com>,
        "H. Peter Anvin" <hpa@...or.com>, Hugh Dickins <hughd@...gle.com>,
        Josh Poimboeuf <jpoimboe@...hat.com>,
        Kees Cook <keescook@...gle.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Michael Schwarz <michael.schwarz@...k.tugraz.at>,
        Moritz Lipp <moritz.lipp@...k.tugraz.at>,
        Peter Zijlstra <peterz@...radead.org>,
        Richard Fellner <richard.fellner@...dent.tugraz.at>,
        Thomas Gleixner <tglx@...utronix.de>,
        LKML <linux-kernel@...r.kernel.org>, tipbuild@...or.com,
        lkp@...org
Subject: Re: [x86/mm/kaiser]  a6c70b8b30:
 WARNING:at_kernel/locking/lockdep.c:#trace_hardirqs_off_caller

On Fri, Nov 24, 2017 at 03:02:33PM +0100, Ingo Molnar wrote:
>
>* kernel test robot <fengguang.wu@...el.com> wrote:
>
>>
>> FYI, we noticed the following commit (built with gcc-6):
>>
>> commit: a6c70b8b30bf35045d14e352bfd1eb16aaee906f ("x86/mm/kaiser: Prepare assembly for entry/exit CR3 switching")
>> https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git WIP.x86/mm
>
>Should be fixed in the latest version - please let me know if it isn't.

Yes it's indeed fixed!

Thanks,
Fengguang