From: kernel test robot <lkp@intel.com>
To: Qi Zheng <zhengqi.arch@bytedance.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Kees Cook <keescook@chromium.org>
Subject: [kees:fix/wchan/leaky 5/6] arch/x86/kernel/process.c:952:2: error: implicit declaration of function 'stack_trace_save_tsk'
Date: Wed, 10 Nov 2021 06:16:05 +0800 [thread overview]
Message-ID: <202111100657.lYm2CN4x-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1964 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git fix/wchan/leaky
head: 62ba17f8f461578402c62e7cc2318443a262cc3b
commit: 26a28d75580ddecc5d085def97bbd76c4f60f0a3 [5/6] x86: Fix get_wchan() to support the ORC unwinder
config: x86_64-alldefconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?id=26a28d75580ddecc5d085def97bbd76c4f60f0a3
git remote add kees https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git
git fetch --no-tags kees fix/wchan/leaky
git checkout 26a28d75580ddecc5d085def97bbd76c4f60f0a3
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
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/x86/kernel/process.c: In function 'get_wchan':
>> arch/x86/kernel/process.c:952:2: error: implicit declaration of function 'stack_trace_save_tsk' [-Werror=implicit-function-declaration]
952 | stack_trace_save_tsk(p, &entry, 1, 0);
| ^~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/stack_trace_save_tsk +952 arch/x86/kernel/process.c
938
939 /*
940 * Called from fs/proc with a reference on @p to find the function
941 * which called into schedule(). This needs to be done carefully
942 * because the task might wake up and we might look at a stack
943 * changing under us.
944 */
945 unsigned long get_wchan(struct task_struct *p)
946 {
947 unsigned long entry = 0;
948
949 if (p == current || task_is_running(p))
950 return 0;
951
> 952 stack_trace_save_tsk(p, &entry, 1, 0);
953 return entry;
954 }
955
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 16730 bytes --]
reply other threads:[~2021-11-09 22:17 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=202111100657.lYm2CN4x-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhengqi.arch@bytedance.com \
/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
all inboxes | Powered by JetHome®