Re: linux-next: build failure after merge of the tip tree

Mark Brown
2026-03-11T16:25:34Z

[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]

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>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]