[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+G9fYvEANOMekjvtu7agdVYQ_b8OMtxQdyAV2JT_vMdBU3VRA@mail.gmail.com>
Date: Fri, 11 Mar 2022 02:47:54 +0530
From: Naresh Kamboju <naresh.kamboju@...aro.org>
To: Ard Biesheuvel <ardb@...nel.org>,
"Russell King (Oracle)" <linux@...linux.org.uk>
Cc: 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
Hi Ard and Russell,
The boot test pass on linux next-20220310 tag with KASAN=y on BeagleBoard x15
device. but LTP cve tests reproduced the reported kernel crash [1].
>From the available historical data I can confirm that this is an
intermittent issue on
BeagleBoard x15 devices.
OTOH, the kernel crash is always reproducible on qemu-arm with KASAN=y
while booting which has been known to fail for a long time.
>From the Ardb tree I have boot tested qemu-arm with KASAN=y the reported
kernel crash is always reproducible.
The build steps [3] and extra Kconfigs.
- Naresh
[1] https://lkft.validation.linaro.org/scheduler/job/4701310
[2] https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/
[3] https://builds.tuxbuild.com/2661dIAPUjE2DMJvye91He2gus0/tuxmake_reproducer.sh
Powered by blists - more mailing lists