On Tue, Nov 04, 2025 at 09:44:38AM +0100, Marek Szyprowski wrote:
> On 03.11.2025 16:24, Mark Brown wrote:

> > We do have some other serious breakage affecting arm64 in -next which
> > are making it hard to get a clear picture of which platforms are
> > affected, at least the FVP and O6 are unaffected by those other issues
> > (due to using MTE on platforms that don't have it, those platforms do
> > have MTE).

> I got almost the same result while bisecting on ARM 32bit Exynos-based 
> boards, so the issue with this patchset is not fully ARM64 specific. For 
> some reasons it also doesn't affect all systems though. It is even 
> worse, because it affected only a subset of boards, but different for 
> each tested commit. The observed failure looks exactly the same:

I've now got the results for this specific commit, it looks like every
single arm64 system is failing.  I didn't test any other architectures.

> Then I've tested it on ARM64bit (RaspberrryPi3b+ board) and got the 
> following panic on 6a011a228293 ("vdso/datastore: Map pages through 
> struct page") commit:

I'm seeing the same thing on at least some of the systems - this is with
arm64 defconfig (I suspect that's what Marek is doing too).  For
example:

   https://lava.sirena.org.uk/scheduler/job/2039543#L1109

I didn't check every single failure.  Feeding one of the backtraces
through addr2line says:

/build/stage/linux/include/linux/page-flags.h:284 (discriminator 2)
/build/stage/linux/mm/mmap.c:1438
/build/stage/linux/mm/memory.c:5280
/build/stage/linux/mm/memory.c:5698
/build/stage/linux/mm/memory.c:6487
/build/stage/linux/arch/arm64/mm/fault.c:696
/build/stage/linux/arch/arm64/mm/fault.c:793
/build/stage/linux/arch/arm64/mm/fault.c:929 (discriminator 1)
/build/stage/linux/arch/arm64/include/asm/irqflags.h:55
/build/stage/linux/arch/arm64/kernel/entry-common.c:767
/build/stage/linux/arch/arm64/kernel/entry.S:596

(this is for this specific commit.)

Attachment: signature.asc
Description: PGP signature

Reply via email to