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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <576e6cd1-7009-4823-83e2-bfc66fd786e1@sirena.org.uk>
Date: Mon, 19 Jan 2026 16:43:46 +0000
From: Mark Brown <broonie@...nel.org>
To: James Clark <james.clark@...aro.org>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>,
	Namhyung Kim <namhyung@...nel.org>, Leo Yan <leo.yan@....com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the perf tree

On Mon, Jan 19, 2026 at 04:37:12PM +0000, James Clark wrote:
> On 19/01/2026 4:09 pm, Mark Brown wrote:

> > After merging the perf tree, today's linux-next build (arm64 perf)
> > failed like this:

> > Exception processing /tmp/next/perf/pmu-events/arch/arm64/arm/cortex-a510/pmu.json

> Do you have a clean checkout? a66f6242fbf52 removes this file and at the
> same time removes the definition from common-and-microarch.json. I think you
> would get this build error if cortex-a510/pmu.json exists as a stale file
> with that commit applied.

No, all the -next builds are done incrementally so the working tree will
start with whatever the last commit that got built was.  This would also
break bisection cases...

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)