From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH v7 1/4] arm64: Make all stack walking functions use arch_stack_walk()
Date: Fri, 13 Aug 2021 04:59:26 +0800 [thread overview]
Message-ID: <202108130415.nNVejQFP-lkp@intel.com> (raw)
In-Reply-To: <20210812132435.6143-2-madvenka@linux.microsoft.com>
[-- Attachment #1: Type: text/plain, Size: 4576 bytes --]
Hi,
[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on v5.14-rc5]
[also build test ERROR on next-20210812]
[cannot apply to arm64/for-next/core tip/perf/core]
[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]
url: https://github.com/0day-ci/linux/commits/madvenka-linux-microsoft-com/arm64-Make-all-stack-walking-functions-use-arch_stack_walk/20210812-222448
base: 36a21d51725af2ce0700c6ebcb6b9594aac658a6
config: arm64-defconfig (attached as .config)
compiler: aarch64-linux-gcc (GCC) 10.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/560d91e019f24a55c3d254f967eb27e4ed4992e1
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review madvenka-linux-microsoft-com/arm64-Make-all-stack-walking-functions-use-arch_stack_walk/20210812-222448
git checkout 560d91e019f24a55c3d254f967eb27e4ed4992e1
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
arch/arm64/kernel/perf_callchain.c: In function 'perf_callchain_kernel':
>> arch/arm64/kernel/perf_callchain.c:155:2: error: implicit declaration of function 'arch_stack_walk' [-Werror=implicit-function-declaration]
155 | arch_stack_walk(callchain_trace, entry, current, regs);
| ^~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
--
arch/arm64/kernel/process.c: In function 'get_wchan':
>> arch/arm64/kernel/process.c:578:2: error: implicit declaration of function 'arch_stack_walk' [-Werror=implicit-function-declaration]
578 | arch_stack_walk(get_wchan_cb, &wchan_info, p, NULL);
| ^~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
--
arch/arm64/kernel/stacktrace.c:66:13: warning: no previous prototype for 'unwind_frame' [-Wmissing-prototypes]
66 | int notrace unwind_frame(struct task_struct *tsk, struct stackframe *frame)
| ^~~~~~~~~~~~
arch/arm64/kernel/stacktrace.c:139:14: warning: no previous prototype for 'walk_stackframe' [-Wmissing-prototypes]
139 | void notrace walk_stackframe(struct task_struct *tsk, struct stackframe *frame,
| ^~~~~~~~~~~~~~~
arch/arm64/kernel/stacktrace.c: In function 'dump_backtrace':
>> arch/arm64/kernel/stacktrace.c:178:2: error: implicit declaration of function 'arch_stack_walk' [-Werror=implicit-function-declaration]
178 | arch_stack_walk(dump_backtrace_entry, (void *)loglvl, tsk, regs);
| ^~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
--
arch/arm64/kernel/time.c: In function 'profile_pc':
>> arch/arm64/kernel/time.c:52:2: error: implicit declaration of function 'arch_stack_walk' [-Werror=implicit-function-declaration]
52 | arch_stack_walk(profile_pc_cb, &prof_pc, current, regs);
| ^~~~~~~~~~~~~~~
arch/arm64/kernel/time.c: At top level:
arch/arm64/kernel/time.c:58:13: warning: no previous prototype for 'time_init' [-Wmissing-prototypes]
58 | void __init time_init(void)
| ^~~~~~~~~
cc1: some warnings being treated as errors
--
arch/arm64/kernel/return_address.c: In function 'return_address':
>> arch/arm64/kernel/return_address.c:42:2: error: implicit declaration of function 'arch_stack_walk' [-Werror=implicit-function-declaration]
42 | arch_stack_walk(save_return_addr, &data, current, NULL);
| ^~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/arch_stack_walk +155 arch/arm64/kernel/perf_callchain.c
146
147 void perf_callchain_kernel(struct perf_callchain_entry_ctx *entry,
148 struct pt_regs *regs)
149 {
150 if (perf_guest_cbs && perf_guest_cbs->is_in_guest()) {
151 /* We don't support guest os callchain now */
152 return;
153 }
154
> 155 arch_stack_walk(callchain_trace, entry, current, regs);
156 }
157
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 55147 bytes --]
next prev parent reply other threads:[~2021-08-12 20:59 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3f2aab69a35c243c5e97f47c4ad84046355f5b90>
2021-06-30 22:33 ` [RFC PATCH v6 0/3] arm64: Implement stack trace reliability checks madvenka
2021-06-30 22:33 ` madvenka
2021-06-30 22:33 ` [RFC PATCH v6 1/3] arm64: Improve the unwinder return value madvenka
2021-06-30 22:33 ` madvenka
2021-07-28 16:56 ` Mark Rutland
2021-07-28 16:56 ` Mark Rutland
2021-07-29 13:54 ` Madhavan T. Venkataraman
2021-07-29 13:54 ` Madhavan T. Venkataraman
2021-06-30 22:33 ` [RFC PATCH v6 2/3] arm64: Introduce stack trace reliability checks in the unwinder madvenka
2021-06-30 22:33 ` madvenka
2021-06-30 22:33 ` [RFC PATCH v6 3/3] arm64: Create a list of SYM_CODE functions, check return PC against list madvenka
2021-06-30 22:33 ` madvenka
2021-07-28 17:25 ` Mark Rutland
2021-07-28 17:25 ` Mark Rutland
2021-07-29 14:06 ` Madhavan T. Venkataraman
2021-07-29 14:06 ` Madhavan T. Venkataraman
2021-07-29 14:52 ` Mark Brown
2021-07-29 14:52 ` Mark Brown
2021-07-29 17:07 ` Madhavan T. Venkataraman
2021-07-29 17:07 ` Madhavan T. Venkataraman
2021-07-29 15:48 ` Mark Rutland
2021-07-29 15:48 ` Mark Rutland
2021-07-29 16:27 ` Mark Brown
2021-07-29 16:27 ` Mark Brown
2021-07-29 17:09 ` Madhavan T. Venkataraman
2021-07-29 17:09 ` Madhavan T. Venkataraman
2021-07-26 13:49 ` [RFC PATCH v6 0/3] arm64: Implement stack trace reliability checks Madhavan T. Venkataraman
2021-07-26 13:49 ` Madhavan T. Venkataraman
2021-08-12 13:24 ` [RFC PATCH v7 0/4] arm64: Reorganize the unwinder and implement " madvenka
2021-08-12 13:24 ` madvenka
2021-08-12 13:24 ` [RFC PATCH v7 1/4] arm64: Make all stack walking functions use arch_stack_walk() madvenka
2021-08-12 13:24 ` madvenka
2021-08-12 15:23 ` Mark Brown
2021-08-12 15:23 ` Mark Brown
2021-08-12 16:30 ` Madhavan T. Venkataraman
2021-08-12 16:30 ` Madhavan T. Venkataraman
2021-08-12 20:59 ` kernel test robot [this message]
2021-08-12 13:24 ` [RFC PATCH v7 2/4] arm64: Reorganize the unwinder code for better consistency and maintenance madvenka
2021-08-12 13:24 ` madvenka
2021-08-12 13:24 ` [RFC PATCH v7 3/4] arm64: Introduce stack trace reliability checks in the unwinder madvenka
2021-08-12 13:24 ` madvenka
2021-08-12 13:24 ` [RFC PATCH v7 4/4] arm64: Create a list of SYM_CODE functions, check return PC against list madvenka
2021-08-12 13:24 ` madvenka
2021-08-12 18:53 ` kernel test robot
2021-08-12 18:31 ` [RFC PATCH v7 0/4] arm64: Reorganize the unwinder and implement stack trace reliability checks Madhavan T. Venkataraman
2021-08-12 18:31 ` Madhavan T. Venkataraman
2021-08-12 18:45 ` Madhavan T. Venkataraman
2021-08-12 18:45 ` Madhavan T. Venkataraman
2021-08-12 18:35 ` madvenka
2021-08-12 18:35 ` madvenka
2021-08-12 18:35 ` [RFC PATCH v7 1/4] arm64: Make all stack walking functions use arch_stack_walk() madvenka
2021-08-12 18:35 ` madvenka
2021-08-12 18:35 ` [RFC PATCH v7 2/4] arm64: Reorganize the unwinder code for better consistency and maintenance madvenka
2021-08-12 18:35 ` madvenka
2021-08-12 18:35 ` [RFC PATCH v7 3/4] arm64: Introduce stack trace reliability checks in the unwinder madvenka
2021-08-12 18:35 ` madvenka
2021-08-12 18:35 ` [RFC PATCH v7 4/4] arm64: Create a list of SYM_CODE functions, check return PC against list madvenka
2021-08-12 18:35 ` madvenka
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=202108130415.nNVejQFP-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.