linux-kernel - Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word

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]

Date:   Wed, 9 Mar 2022 15:57:32 +0100
From:   Ard Biesheuvel <ardb@...nel.org>
To:     Naresh Kamboju <naresh.kamboju@...aro.org>
Cc:     "Russell King (Oracle)" <linux@...linux.org.uk>,
        open list <linux-kernel@...r.kernel.org>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        Linus Walleij <linus.walleij@...aro.org>,
        Arnd Bergmann <arnd@...db.de>,
        Corentin Labbe <clabbe.montjoie@...il.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck

On Wed, 9 Mar 2022 at 15:44, Naresh Kamboju <naresh.kamboju@...aro.org> wrote:
>
> On Wed, 9 Mar 2022 at 19:37, Naresh Kamboju <naresh.kamboju@...aro.org> wrote:
> >
> > On Wed, 9 Mar 2022 at 16:16, Ard Biesheuvel <ardb@...nel.org> wrote:
> > >
> > > On Wed, 9 Mar 2022 at 11:37, Russell King (Oracle)
> > > <linux@...linux.org.uk> wrote:
> > > >
> > > > On Wed, Mar 09, 2022 at 03:18:12PM +0530, Naresh Kamboju wrote:
> > > > > While boting linux next-20220308 on BeagleBoard-X15 and qemu arm the following
> > > > > kernel crash reported which is CONFIG_KASAN enabled build [1] & [2].
> > > >
> > > > The unwinder is currently broken in linux-next. Please try reverting
> > > > 532319b9c418 ("ARM: unwind: disregard unwind info before stack frame is
> > > > set up")
>
> I have reverted the suggested commit and built and boot failed due to reported
> kernel crash [1].
>
> - Naresh
>

Thanks Naresh,

This looks like it might be related to the issue Russell just sent a fix for:
https://lore.kernel.org/linux-arm-kernel/CAMj1kXEqp2UmsyUe1eWErtpMk3dGEFZyyno3nqydC_ML0bwTLw@mail.gmail.com/T/#t

Could you please try that?