Subject: Re: linux-next: build failure after merge of the mm-hotfixes tree

From: "David Hildenbrand (Arm)" <[email-masked]>
Date: Tue, 21 Apr 2026 15:28:59 +0200

On 4/21/26 15:21, Mark Brown wrote:
> On Tue, Apr 21, 2026 at 03:06:32PM +0200, David Hildenbrand (Arm) wrote:
>> On 4/21/26 14:59, Mark Brown wrote:
> 
>>> After merging the mm-hotfixes tree, today's linux-next build (arm64
>>> allnoconfig) failed like this:
> 
>>> ld: Unexpected GOT/PLT entries detected!
>>> ld: Unexpected run-time procedure linkages detected!
>>> ld: arch/arm64/mm/fault.o: in function `tag_clear_highpages':
>>> fault.c:(.text+0xc40): undefined reference to `mte_clear_page_tags'
> 
>>> Caused by commit
> 
>>>   99e63a49650cc (mm/page_alloc: fix initialization of tags of the huge zero folio with init_on_free)
> 
>> The patch will get resent (and should not have immediately been queued
>> in the mm-hotfixes branch).
> 
>> Feel free to drop the patch on your tree.
> 
> To be clear linux-next merges the trees that maintainers are publishing,
> the standard fix for straight failures like this is to merge the last
> version that worked.  Sometimes reverts do get applied but more usually
> for things that only come up in the final builds.

If that unblocks you, great.

> 
>>> I have used the version from next-20260420 instead.  The commit removed
> 
> The commit is also present in the mm-unstable tree, I have also used
> the version of that from 20260420.

Yeah, it should have landed on mm-new first for 1/2 days.

-- 
Cheers,

David