From: kernel test robot <lkp@intel.com>
To: Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 13538/13721] mm/kasan/common.c:601:21: error: 'KASAN_VMALLOC_KEEP_TAG' undeclared; did you mean 'KASAN_VMALLOC_PAGE_RANGE'?
Date: Tue, 9 Dec 2025 00:43:18 +0800 [thread overview]
Message-ID: <202512090010.3nvGK9yw-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 82bcd04d124a4d84580ea4a8ba6b120db5f512e7
commit: 6b83afdcfa935db4f836906ca7f0fcafdca8d229 [13538/13721] kasan: unpoison vms[area] addresses with a common tag
config: um-allyesconfig (https://download.01.org/0day-ci/archive/20251209/202512090010.3nvGK9yw-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251209/202512090010.3nvGK9yw-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202512090010.3nvGK9yw-lkp@intel.com/
Note: the linux-next/master HEAD 82bcd04d124a4d84580ea4a8ba6b120db5f512e7 builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
mm/kasan/common.c: In function '__kasan_unpoison_vmap_areas':
>> mm/kasan/common.c:601:21: error: 'KASAN_VMALLOC_KEEP_TAG' undeclared (first use in this function); did you mean 'KASAN_VMALLOC_PAGE_RANGE'?
601 | if (flags & KASAN_VMALLOC_KEEP_TAG) {
| ^~~~~~~~~~~~~~~~~~~~~~
| KASAN_VMALLOC_PAGE_RANGE
mm/kasan/common.c:601:21: note: each undeclared identifier is reported only once for each function it appears in
vim +601 mm/kasan/common.c
586
587 #ifdef CONFIG_KASAN_VMALLOC
588 void __kasan_unpoison_vmap_areas(struct vm_struct **vms, int nr_vms,
589 kasan_vmalloc_flags_t flags)
590 {
591 unsigned long size;
592 void *addr;
593 int area;
594 u8 tag;
595
596 /*
597 * If KASAN_VMALLOC_KEEP_TAG was set at this point, all vms[] pointers
598 * would be unpoisoned with the KASAN_TAG_KERNEL which would disable
599 * KASAN checks down the line.
600 */
> 601 if (flags & KASAN_VMALLOC_KEEP_TAG) {
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-08 16:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202512090010.3nvGK9yw-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=maciej.wieczor-retman@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox