From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android16-6.12 2/2] ERROR: modpost: "kasan_inval_dcache" [mm/kasan/kasan_test.ko] undefined!
Date: Mon, 31 Mar 2025 11:23:57 +0800 [thread overview]
Message-ID: <202503311128.w8jZhNDL-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android16-6.12
head: b007708642feb84db41492468392d502f8eff553
commit: 8d99997b19ad09073cb0bbbe68bc6ac02ef58ca1 [2/2] ANDROID: kasan: flush dcache after tag writes
config: arm64-randconfig-002-20250331 (https://download.01.org/0day-ci/archive/20250331/202503311128.w8jZhNDL-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project 7eccafc3c84606587a175c0a8c1ebea6e4fb21cd)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250331/202503311128.w8jZhNDL-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/202503311128.w8jZhNDL-lkp@intel.com/
All errors (new ones prefixed by >>, old ones prefixed by <<):
WARNING: modpost: missing MODULE_DESCRIPTION() in mm/kasan/kasan_test.o
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/xen/xenbus/xenbus_probe_frontend.o
>> ERROR: modpost: "kasan_inval_dcache" [mm/kasan/kasan_test.ko] undefined!
>> ERROR: modpost: "dcache_clean_inval_poc" [mm/kasan/kasan_test.ko] undefined!
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-03-31 3:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 3:23 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-23 12:33 [android-common:android16-6.12 2/2] ERROR: modpost: "kasan_inval_dcache" [mm/kasan/kasan_test.ko] undefined! kernel test robot
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=202503311128.w8jZhNDL-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.