linux-kernel - Re: linux-next: boot failure after merge of the tip tree

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: <20230524093454.GI4253@hirez.programming.kicks-ass.net>
Date:   Wed, 24 May 2023 11:34:54 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        "H. Peter Anvin" <hpa@...or.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Michael Ellerman <mpe@...erman.id.au>,
        PowerPC <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: linux-next: boot failure after merge of the tip tree

On Wed, May 24, 2023 at 03:44:59PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the tip tree, today's linux-next build (powerpc
> pseries_le_defconfig) failed to boot like this:
> 
>  Built 1 zonelists, mobility grouping on.  Total pages: 32736
>  Policy zone: Normal
>  mem auto-init: stack:all(zero), heap alloc:off, heap free:off
>  Memory: 2027392K/2097152K available (17984K kernel code, 3328K rwdata, 14784K rodata, 6080K init, 1671K bss, 69760K reserved, 0K cma-reserved)
> 
> *crickets*
> 
> Bisected to commit
> 
>   f4ab23558310 ("slub: Replace cmpxchg_double()")
> 
> I have reverted that commit (and the following one) for today.

Sorry about that; turns out I forgot to test the case where cmpxchg128
wasn't available.

Please see:

  https://lkml.kernel.org/r/20230524093246.GP83892@hirez.programming.kicks-ass.net

As stated there, I'm going to zap tip/locking/core for a few days and
let this fixed version run through the robots again before re-instating
it.