linux-kernel - Re: [BUG] WARNING: CPU: 3 PID: 1 at mm/debug_vm

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: <20211013102716.4a7c3800@gandalf.local.home>
Date:   Wed, 13 Oct 2021 10:27:16 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Anshuman Khandual <anshuman.khandual@....com>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Dave Hansen <dave.hansen@...ux.intel.com>,
        Andy Lutomirski <luto@...nel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Borislav Petkov <bp@...en8.de>,
        LKML <linux-kernel@...r.kernel.org>,
        Gavin Shan <gshan@...hat.com>,
        Christophe Leroy <christophe.leroy@...roup.eu>,
        Gerald Schaefer <gerald.schaefer@...ux.ibm.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        the arch/x86 maintainers <x86@...nel.org>
Subject: Re: [BUG] WARNING: CPU: 3 PID: 1 at mm/debug_vm_pgtable.c:493

On Wed, 13 Oct 2021 09:40:11 +0530
Anshuman Khandual <anshuman.khandual@....com> wrote:

> I have run this test on x86 platform many times before (although not recently)
> without any problem and never had this bug report before. Wondering if there
> are recent changes on x86 platform, causing these warning.

As noticed in my conversation with Linus, this warning was there before
your updates, as it was in 5.14-rc2.

> 
> Gavin,
> 
> Although unlikely, was there something on the series which might have
> changed pud_huge_tests() ?

Not sure. But my test box that triggers this is open now, and I'll add
Linus's debug patch and see if I can retrigger it.

-- Steve