linux-kernel - Re: REGRESSION: kernel BUG at arch/arm64/kernel/alternative.c:157!

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]

Message-ID: <CALAqxLXNq__ycVa1GJMYd-gx2cEXzkY-ipd1qe5S=4i+xP8c3A@mail.gmail.com>
Date:   Wed, 19 May 2021 18:16:46 -0700
From:   John Stultz <john.stultz@...aro.org>
To:     Will Deacon <will@...nel.org>
Cc:     Catalin Marinas <catalin.marinas@....com>,
        Kees Cook <keescook@...omium.org>,
        Sami Tolvanen <samitolvanen@...gle.com>,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        YongQin Liu <yongqin.liu@...aro.org>,
        Amit Pundir <amit.pundir@...aro.org>,
        Mark Rutland <mark.rutland@....com>,
        Mark Brown <broonie@...nel.org>,
        Masahiro Yamada <masahiroy@...nel.org>,
        Marc Zyngier <maz@...nel.org>
Subject: Re: REGRESSION: kernel BUG at arch/arm64/kernel/alternative.c:157!

On Tue, May 18, 2021 at 1:49 AM Will Deacon <will@...nel.org> wrote:
>
> Hi John,
>
> On Mon, May 17, 2021 at 02:52:59PM -0700, John Stultz wrote:
> > With v5.13-rc2, I've been seeing an odd boot regression with the
> > DragonBoard 845c:
> >
> > Unfortunately, trying to bisect it down (v5.13-rc1 works ok) is giving
> > me inconsistent results so far. It feels a bit like maybe some config
> > option gets enabled moving forward, and then sticks around when we go
> > back.  I'll take another swing at bisecting it later today, but I have
> > to move on to some other work right now, so I figured I'd share (with
> > folks who better know the recent __apply_alternatives changes) in case
> > folks have a better idea:
>
> Please can you try reverting af44068c581c and 0c6c2d3615ef?

Hey Will,
  I realized I didn't get back to you on this.  As MarkR already noted
it does seem to be coming from 0c6c2d3615ef. Jumping to 5.13-rc1,
doing a make clean, building/booting then jumping to 5.13-rc2 + the
two reverts above, building/booting, and the issue won't appear. If we
just jump to 5.13-rc2 or 5.13-rc2 with af44068c581c reverted, after
building and booting I'll be able to see the issue.

 Given it disappears after a make clean, I'm guessing this isn't a
major issue, mostly just a concern for folks to accidently hit it
bisecting things, so I'm not sure if there's anything else to do.

Let me know if you'd like me to try anything else.

thanks
-john