On Thu, 10 Mar 2022 at 22:50, Naresh Kamboju <naresh.kamboju@xxxxxxxxxx> wrote: > > On Fri, 11 Mar 2022 at 02:55, Ard Biesheuvel <ardb@xxxxxxxxxx> wrote: > > > > On Thu, 10 Mar 2022 at 22:18, Naresh Kamboju <naresh.kamboju@xxxxxxxxxx> wrote: > > > > > > 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 > > > > Thanks Naresh. I'm having trouble to make sense of this, though. The > > linked output log appears to be from a build that lacks my 'ARM: > > entry: fix unwinder problems caused by IRQ stacks' patch, as it > > doesn't show any occurrences of call_with_stack() on any of the call > > stacks. > > > > Do you have a link to the vmlinux and zImage files for this build? > > Yes. > > vmlinux.xz: https://builds.tuxbuild.com/26BmIasJnAyCii0SkgbKarkF369/vmlinux.xz > zImage: https://builds.tuxbuild.com/26BmIasJnAyCii0SkgbKarkF369/zImage > System.map: https://builds.tuxbuild.com/26BmIasJnAyCii0SkgbKarkF369/System.map > Build log: https://builds.tuxbuild.com/26BmIasJnAyCii0SkgbKarkF369/ > This kernel does not appear to have ARM: unwind: set frame.pc correctly for current-thread unwinding ARM: entry: fix unwinder problems caused by IRQ stacks ARM: Revert "unwind: dump exception stack from calling frame" so it is expected that the same issue is still being observed. Could you please try -next with those patches applied?
