From: kernel test robot <lkp@intel.com>
To: Yunhui Cui <cuiyunhui@bytedance.com>,
aou@eecs.berkeley.edu, alex@ghiti.fr, andii@kernel.org,
andybnac@gmail.com, apatel@ventanamicro.com, ast@kernel.org,
ben.dooks@codethink.co.uk, bjorn@kernel.org, bpf@vger.kernel.org,
charlie@rivosinc.com, cl@gentwo.org, conor.dooley@microchip.com,
cyrilbur@tenstorrent.com, daniel@iogearbox.net,
debug@rivosinc.com, dennis@kernel.org, eddyz87@gmail.com,
haoluo@google.com, john.fastabend@gmail.com, jolsa@kernel.org,
kpsingh@kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-riscv@lists.infradead.org,
linux@rasmusvillemoes.dk, martin.lau@linux.dev,
palmer@dabbelt.com, pjw@kernel.org, puranjay@kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v2 2/3] riscv: introduce percpu.h into include/asm
Date: Tue, 9 Dec 2025 11:55:54 +0800 [thread overview]
Message-ID: <202512091137.3Qw1dX94-lkp@intel.com> (raw)
In-Reply-To: <20251208034944.73113-3-cuiyunhui@bytedance.com>
Hi Yunhui,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.18 next-20251209]
[cannot apply to bpf-next/net bpf-next/master bpf/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Yunhui-Cui/riscv-remove-irqflags-h-inclusion-in-asm-bitops-h/20251208-115407
base: linus/master
patch link: https://lore.kernel.org/r/20251208034944.73113-3-cuiyunhui%40bytedance.com
patch subject: [PATCH v2 2/3] riscv: introduce percpu.h into include/asm
config: riscv-randconfig-002-20251209 (https://download.01.org/0day-ci/archive/20251209/202512091137.3Qw1dX94-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251209/202512091137.3Qw1dX94-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/202512091137.3Qw1dX94-lkp@intel.com/
All errors (new ones prefixed by >>):
>> mm/slub.c:4380:9: error: call to undeclared function 'arch_cmpxchg128_local'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
4380 | return this_cpu_try_cmpxchg_freelist(s->cpu_slab->freelist_tid,
| ^
mm/slab.h:24:39: note: expanded from macro 'this_cpu_try_cmpxchg_freelist'
24 | #define this_cpu_try_cmpxchg_freelist this_cpu_try_cmpxchg128
| ^
include/asm-generic/percpu.h:529:47: note: expanded from macro 'this_cpu_try_cmpxchg128'
529 | __cpu_fallback_try_cmpxchg(pcp, ovalp, nval, this_cpu_cmpxchg128)
| ^
1 error generated.
vim +/arch_cmpxchg128_local +4380 mm/slub.c
0b303fb402862d Vlastimil Babka 2021-05-08 4371
6801be4f2653e5 Peter Zijlstra 2023-05-31 4372 static inline bool
6801be4f2653e5 Peter Zijlstra 2023-05-31 4373 __update_cpu_freelist_fast(struct kmem_cache *s,
6801be4f2653e5 Peter Zijlstra 2023-05-31 4374 void *freelist_old, void *freelist_new,
6801be4f2653e5 Peter Zijlstra 2023-05-31 4375 unsigned long tid)
6801be4f2653e5 Peter Zijlstra 2023-05-31 4376 {
b244358e9a1cd6 Vlastimil Babka 2025-11-07 4377 struct freelist_tid old = { .freelist = freelist_old, .tid = tid };
b244358e9a1cd6 Vlastimil Babka 2025-11-07 4378 struct freelist_tid new = { .freelist = freelist_new, .tid = next_tid(tid) };
6801be4f2653e5 Peter Zijlstra 2023-05-31 4379
b244358e9a1cd6 Vlastimil Babka 2025-11-07 @4380 return this_cpu_try_cmpxchg_freelist(s->cpu_slab->freelist_tid,
b244358e9a1cd6 Vlastimil Babka 2025-11-07 4381 &old.freelist_tid, new.freelist_tid);
6801be4f2653e5 Peter Zijlstra 2023-05-31 4382 }
6801be4f2653e5 Peter Zijlstra 2023-05-31 4383
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-12-09 3:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 3:49 [PATCH v2 0/3] RISC-V: add percpu.h to include/asm Yunhui Cui
2025-12-08 3:49 ` [PATCH v2 1/3] riscv: remove irqflags.h inclusion in asm/bitops.h Yunhui Cui
2025-12-08 3:49 ` [PATCH v2 2/3] riscv: introduce percpu.h into include/asm Yunhui Cui
2025-12-09 2:12 ` kernel test robot
2025-12-09 3:55 ` kernel test robot [this message]
2025-12-09 18:05 ` kernel test robot
2025-12-08 3:49 ` [PATCH v2 3/3] riscv: store percpu offset into thread_info Yunhui Cui
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=202512091137.3Qw1dX94-lkp@intel.com \
--to=lkp@intel.com \
--cc=alex@ghiti.fr \
--cc=andii@kernel.org \
--cc=andybnac@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=ast@kernel.org \
--cc=ben.dooks@codethink.co.uk \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=charlie@rivosinc.com \
--cc=cl@gentwo.org \
--cc=conor.dooley@microchip.com \
--cc=cuiyunhui@bytedance.com \
--cc=cyrilbur@tenstorrent.com \
--cc=daniel@iogearbox.net \
--cc=debug@rivosinc.com \
--cc=dennis@kernel.org \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@rasmusvillemoes.dk \
--cc=llvm@lists.linux.dev \
--cc=martin.lau@linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=puranjay@kernel.org \
/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