linux-kernel - Re: [mm/debug] fa6726c1e7: kernel_BUG_at

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: <31CD915D-2E14-4897-AF62-82B6C5FD567A@lca.pw>
Date:   Mon, 27 Apr 2020 22:05:06 -0400
From:   Qian Cai <cai@....pw>
To:     Anshuman Khandual <Anshuman.Khandual@....com>
Cc:     kernel test robot <lkp@...el.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Christophe Leroy <christophe.leroy@....fr>,
        Catalin Marinas <catalin.marinas@....com>,
        Ingo Molnar <mingo@...nel.org>,
        Mike Rapoport <rppt@...ux.ibm.com>,
        Vineet Gupta <vgupta@...opsys.com>,
        Will Deacon <will@...nel.org>,
        Benjamin Herrenschmidt <benh@...nel.crashing.org>,
        Paul Mackerras <paulus@...ba.org>,
        Michael Ellerman <mpe@...erman.id.au>,
        Heiko Carstens <heiko.carstens@...ibm.com>,
        Vasily Gorbik <gor@...ux.ibm.com>,
        Christian Borntraeger <borntraeger@...ibm.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
        "H. Peter Anvin" <hpa@...or.com>,
        "Kirill A. Shutemov" <kirill@...temov.name>,
        Paul Walmsley <paul.walmsley@...ive.com>,
        Palmer Dabbelt <palmer@...belt.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        LKML <linux-kernel@...r.kernel.org>, lkp@...ts.01.org
Subject: Re: [mm/debug] fa6726c1e7: kernel_BUG_at_include/linux/mm.h



> On Apr 27, 2020, at 9:49 PM, Anshuman Khandual <Anshuman.Khandual@....com> wrote:
> 
> This is an unsupported (enabled via CONFIG_EXPERT) X86 platform (CONFIG_X86_PAE)
> and is known to fail. The latest (V17) patch had moved the test invocation into
> a late_initcall() per Linus thus pushing down any possible failures (like this)
> after early boot. Please ignore this report.
> 
> Apart from this X86_PAE based config, no other platform failures have reported
> so far. Assuming that this test robot does have a good platform coverage, the
> CONFIG_EXPERT method of enabling CONFIG_DEBUG_VM_PGTABLE should help in getting
> more platform coverage for this test.

This sounds really sloppy. Why can’t we make it impossible to select this combination if nobody is willing to fix it?