* Re: linux-next: build failure after merge of the tip tree
[not found] ` <0d21783c-5299-4488-9708-def0b1a4dcbe@sirena.org.uk>
@ 2026-03-12 15:43 ` Ritesh Harjani
0 siblings, 0 replies; only message in thread
From: Ritesh Harjani @ 2026-03-12 15:43 UTC (permalink / raw)
To: Mark Brown, Peter Zijlstra
Cc: Ojaswin Mujoo, Thomas Gleixner, Ingo Molnar, H. Peter Anvin,
Linux Kernel Mailing List, Linux Next Mailing List, willy,
yi.zhang, jack, tytso, linux-ext4
Mark Brown <broonie@kernel.org> writes:
> On Wed, Mar 11, 2026 at 05:09:04PM +0100, Peter Zijlstra wrote:
>> On Wed, Mar 11, 2026 at 08:03:50PM +0530, Ojaswin Mujoo wrote:
>> > On Wed, Mar 11, 2026 at 11:37:43AM +0100, Peter Zijlstra wrote:
>
>> > I believe this issue is resolved with [1]. However, I think this might
>> > not be the same as the issue reported originally as we the original
>> > issue seems to be in mballoc-tests rather than extent-tests. I'll try to
>> > look into it a bit more.
>
>> > [1] https://lore.kernel.org/linux-ext4/5bb9041471dab8ce870c191c19cbe4df57473be8.1772381213.git.ritesh.list@gmail.com/
>
>> I can confirm that solves the KASAN splat; it also cures the defconfig
>> hang that was initially mis-attributed to the mutex patch, but turned
>> out to be memory corruption due to that issue KASAN found.
>
>> FWIW:
>
>> Tested-by: Peter Zijlstra (Intel) <peterz@infradead.org>
>
> Yes, that seems to work for me too - looks like tip just triggers it
> more aggressively for some reason:
>
> Tested-by: Mark Brown <broonie@kernel.org>
Thanks Mark, Peter & Ojaswin for testing.
++linux-ext4 so that if someone observes the same issue in ext4 kunit
tests, they could find this discussion on linux-ext4.
-ritesh
^ permalink raw reply [flat|nested] only message in thread