From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH v1] LoongArch: BPF: Implement arch_bpf_stack_walk()
Date: Tue, 25 Aug 2026 12:13:29 +0800 [thread overview]
Message-ID: <202608251231.fQmOHVs6-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "linux-review patch is more than 7 days old, verify it wasn't already superseded"
::::::
BCC: lkp@intel.com
CC: llvm@lists.linux.dev
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20260813045306.21571-1-yangtiezhu@loongson.cn>
References: <20260813045306.21571-1-yangtiezhu@loongson.cn>
TO: Tiezhu Yang <yangtiezhu@loongson.cn>
TO: Huacai Chen <chenhuacai@kernel.org>
TO: Hengqi Chen <hengqi.chen@gmail.com>
CC: loongarch@lists.linux.dev
CC: bpf@vger.kernel.org
CC: linux-kernel@vger.kernel.org
CC: George Guo <guodongtai@kylinos.cn>
Hi Tiezhu,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20260821]
[also build test ERROR on linus/master]
[cannot apply to bpf-next/master bpf/master bpf-next/net v7.2 v7.2-rc7 v7.2-rc6 v7.2]
[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/Tiezhu-Yang/LoongArch-BPF-Implement-arch_bpf_stack_walk/20260813-125306
base: next-20260821
patch link: https://lore.kernel.org/r/20260813045306.21571-1-yangtiezhu%40loongson.cn
patch subject: [PATCH v1] LoongArch: BPF: Implement arch_bpf_stack_walk()
:::::: branch date: 12 hours ago
:::::: commit date: 12 hours ago
config: loongarch-defconfig (https://download.01.org/0day-ci/archive/20260825/202608251231.fQmOHVs6-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 935bfc708590c60147a79c7df145bb6e68b1d388)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260825/202608251231.fQmOHVs6-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/r/202608251231.fQmOHVs6-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/loongarch/net/bpf_jit.c:2446:22: error: redefinition of 'walk_bpf_stackframe'
2446 | static noinline void walk_bpf_stackframe(bool (*consume_fn)(void *cookie, u64 ip, u64 sp, u64 bp),
| ^
arch/loongarch/net/bpf_jit.c:2372:22: note: previous definition is here
2372 | static noinline void walk_bpf_stackframe(bool (*consume_fn)(void *cookie, u64 ip, u64 sp, u64 bp),
| ^
>> arch/loongarch/net/bpf_jit.c:2467:6: error: redefinition of 'arch_bpf_stack_walk'
2467 | void arch_bpf_stack_walk(bool (*consume_fn)(void *cookie, u64 ip, u64 sp, u64 bp), void *cookie)
| ^
arch/loongarch/net/bpf_jit.c:2393:6: note: previous definition is here
2393 | void arch_bpf_stack_walk(bool (*consume_fn)(void *cookie, u64 ip, u64 sp, u64 bp), void *cookie)
| ^
2 errors generated.
vim +/walk_bpf_stackframe +2446 arch/loongarch/net/bpf_jit.c
637f7446933b6d George Guo 2026-08-13 2445
637f7446933b6d George Guo 2026-08-13 @2446 static noinline void walk_bpf_stackframe(bool (*consume_fn)(void *cookie, u64 ip, u64 sp, u64 bp),
637f7446933b6d George Guo 2026-08-13 2447 void *cookie, unsigned long fp)
637f7446933b6d George Guo 2026-08-13 2448 {
637f7446933b6d George Guo 2026-08-13 2449 struct pt_regs dummyregs;
637f7446933b6d George Guo 2026-08-13 2450 struct pt_regs *regs = &dummyregs;
637f7446933b6d George Guo 2026-08-13 2451 struct unwind_state state;
637f7446933b6d George Guo 2026-08-13 2452 unsigned long addr;
637f7446933b6d George Guo 2026-08-13 2453
637f7446933b6d George Guo 2026-08-13 2454 regs->regs[3] = (unsigned long)__builtin_frame_address(0);
637f7446933b6d George Guo 2026-08-13 2455 regs->csr_era = (unsigned long)__builtin_return_address(0);
637f7446933b6d George Guo 2026-08-13 2456 regs->regs[1] = 0;
637f7446933b6d George Guo 2026-08-13 2457 regs->regs[22] = fp;
637f7446933b6d George Guo 2026-08-13 2458
637f7446933b6d George Guo 2026-08-13 2459 for (unwind_start(&state, current, regs);
637f7446933b6d George Guo 2026-08-13 2460 !unwind_done(&state); unwind_next_frame(&state)) {
637f7446933b6d George Guo 2026-08-13 2461 addr = unwind_get_return_address(&state);
637f7446933b6d George Guo 2026-08-13 2462 if (!addr || !consume_fn(cookie, (u64)addr, (u64)state.sp, (u64)state.fp))
637f7446933b6d George Guo 2026-08-13 2463 break;
637f7446933b6d George Guo 2026-08-13 2464 }
637f7446933b6d George Guo 2026-08-13 2465 }
637f7446933b6d George Guo 2026-08-13 2466
637f7446933b6d George Guo 2026-08-13 @2467 void arch_bpf_stack_walk(bool (*consume_fn)(void *cookie, u64 ip, u64 sp, u64 bp), void *cookie)
637f7446933b6d George Guo 2026-08-13 2468 {
637f7446933b6d George Guo 2026-08-13 2469 unsigned long fp;
637f7446933b6d George Guo 2026-08-13 2470
637f7446933b6d George Guo 2026-08-13 2471 /*
637f7446933b6d George Guo 2026-08-13 2472 * Capture the live frame pointer ($r22) at the very front-line before
637f7446933b6d George Guo 2026-08-13 2473 * any kernel C code clobbers it. This must be a thin wrapper with no
637f7446933b6d George Guo 2026-08-13 2474 * large stack locals to prevent the compiler from reusing $r22 early.
637f7446933b6d George Guo 2026-08-13 2475 */
637f7446933b6d George Guo 2026-08-13 2476 asm volatile("move %0, $r22" : "=r"(fp));
637f7446933b6d George Guo 2026-08-13 2477 walk_bpf_stackframe(consume_fn, cookie, fp);
637f7446933b6d George Guo 2026-08-13 2478 }
637f7446933b6d George Guo 2026-08-13 2479 #endif /* CONFIG_UNWINDER_ORC */
637f7446933b6d George Guo 2026-08-13 2480
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-08-25 4:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 4:13 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-13 4:53 [PATCH v1] LoongArch: BPF: Implement arch_bpf_stack_walk() Tiezhu Yang
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=202608251231.fQmOHVs6-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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.