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

Maciej Wieczor-Retman
2025-12-08T10:31:05Z

Hi!

This flag, KASAN_VMALLOC_KEEP_TAG was defined in the first patch by Jiayuan in
my three piece series [1]. I looked over git logs in mm-unstable and
mm-hotfixes-unstable and I guess it wasn't pulled there but my two following
patches were.

Could you pull the [1] missing patch Andrew? I think that should fix this issue.
Thanks :)

[1] https://lore.kernel.org/all/247fd641cbf4a8e6c8135051772867f6bd2610ad.1764945396.git.m.wieczorretman@pm.me/

kind regards
Maciej Wieczór-Retman

On 2025-12-08 at 08:35:11 +1100, Stephen Rothwell wrote:
>Hi all,
>
>After merging the mm-hotfixes tree, today's linux-next build (x86_64
>allmodconfig) failed like this:
>
>In file included from arch/x86/include/asm/bug.h:193,
> from include/linux/bug.h:5,
> from include/linux/kasan.h:5,
> from mm/kasan/common.c:14:
>mm/kasan/common.c: In function '__kasan_unpoison_vmap_areas':
>mm/kasan/common.c:594:34: error: 'KASAN_VMALLOC_KEEP_TAG' undeclared (first use in this function); did you mean 'KASAN_VMALLOC_PAGE_RANGE'?
> 594 | if (WARN_ON_ONCE(flags & KASAN_VMALLOC_KEEP_TAG))
> | ^~~~~~~~~~~~~~~~~~~~~~
>include/asm-generic/bug.h:120:32: note: in definition of macro 'WARN_ON_ONCE'
> 120 | int __ret_warn_on = !!(condition); \
> | ^~~~~~~~~
>mm/kasan/common.c:594:34: note: each undeclared identifier is reported only once for each function it appears in
> 594 | if (WARN_ON_ONCE(flags & KASAN_VMALLOC_KEEP_TAG))
> | ^~~~~~~~~~~~~~~~~~~~~~
>include/asm-generic/bug.h:120:32: note: in definition of macro 'WARN_ON_ONCE'
> 120 | int __ret_warn_on = !!(condition); \
> | ^~~~~~~~~
>
>Caused by commit
>
> 6b83afdcfa93 ("kasan: unpoison vms[area] addresses with a common tag")
>
>I have reverted that commit (and the following 2 fixes) for today.
>
>--
>Cheers,
>Stephen Rothwell