From: kernel test robot <lkp@intel.com>
To: Baoquan He <bhe@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [sj:mm-new 39/45] include/linux/atomic/atomic-arch-fallback.h:457:undefined reference to `kasan_flag_enabled'
Date: Fri, 8 Aug 2025 05:00:27 +0200 [thread overview]
Message-ID: <202508080510.f1wPsKSS-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/sj/linux.git mm-new
head: b2a4beca30ba51331a16d7bb84387a70b692a66d
commit: 825af80daf827d439c7dd3e24ef5648cc338bc98 [39/45] mm/kasan: make kasan=on|off take effect for all three modes
config: alpha-randconfig-2003-20250808 (https://download.01.org/0day-ci/archive/20250808/202508080510.f1wPsKSS-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250808/202508080510.f1wPsKSS-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/202508080510.f1wPsKSS-lkp@intel.com/
All errors (new ones prefixed by >>):
alpha-linux-ld: mm/mempool.o: in function `raw_atomic_read':
>> include/linux/atomic/atomic-arch-fallback.h:457:(.text+0x544): undefined reference to `kasan_flag_enabled'
>> alpha-linux-ld: include/linux/atomic/atomic-arch-fallback.h:457:(.text+0x9a8): undefined reference to `kasan_flag_enabled'
vim +457 include/linux/atomic/atomic-arch-fallback.h
e01cc1e8c2ad73 Uros Bizjak 2023-09-25 443
ad8110706f3811 Mark Rutland 2023-06-05 444 /**
ad8110706f3811 Mark Rutland 2023-06-05 445 * raw_atomic_read() - atomic load with relaxed ordering
ad8110706f3811 Mark Rutland 2023-06-05 446 * @v: pointer to atomic_t
ad8110706f3811 Mark Rutland 2023-06-05 447 *
ad8110706f3811 Mark Rutland 2023-06-05 448 * Atomically loads the value of @v with relaxed ordering.
ad8110706f3811 Mark Rutland 2023-06-05 449 *
ad8110706f3811 Mark Rutland 2023-06-05 450 * Safe to use in noinstr code; prefer atomic_read() elsewhere.
ad8110706f3811 Mark Rutland 2023-06-05 451 *
ad8110706f3811 Mark Rutland 2023-06-05 452 * Return: The value loaded from @v.
ad8110706f3811 Mark Rutland 2023-06-05 453 */
1d78814d41701c Mark Rutland 2023-06-05 454 static __always_inline int
1d78814d41701c Mark Rutland 2023-06-05 455 raw_atomic_read(const atomic_t *v)
1d78814d41701c Mark Rutland 2023-06-05 456 {
1d78814d41701c Mark Rutland 2023-06-05 @457 return arch_atomic_read(v);
1d78814d41701c Mark Rutland 2023-06-05 458 }
9257959a6e5b4f Mark Rutland 2023-06-05 459
:::::: The code at line 457 was first introduced by commit
:::::: 1d78814d41701c216e28fcf2656526146dec4a1a locking/atomic: scripts: simplify raw_atomic*() definitions
:::::: TO: Mark Rutland <mark.rutland@arm.com>
:::::: CC: Peter Zijlstra <peterz@infradead.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-08-08 3:01 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=202508080510.f1wPsKSS-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=linux-mm@kvack.org \
--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.