From: kbuild test robot <lkp@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org, tipbuild@zytor.com
Subject: [tip:WIP.core/stacktrace 4/32] include/linux/stacktrace.h:65:10: error: 'ENOSYS' undeclared
Date: Tue, 16 Apr 2019 18:12:14 +0800 [thread overview]
Message-ID: <201904161849.959pvukz%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2230 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.core/stacktrace
head: 9fe290aca53f59fd24187841dd4a8ff41ade91bd
commit: 714f46ba649b163e80d3dd89e83b92f4ba5ac6af [4/32] stacktrace: Provide helpers for common stack trace operations
config: i386-randconfig-x010-201915 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
git checkout 714f46ba649b163e80d3dd89e83b92f4ba5ac6af
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
In file included from include/linux/lockdep.h:29:0,
from include/linux/spinlock_types.h:18,
from kernel/bounds.c:14:
include/linux/stacktrace.h:62:19: error: static declaration of 'save_stack_trace_tsk_reliable' follows non-static declaration
static inline int save_stack_trace_tsk_reliable(struct task_struct *tsk,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/stacktrace.h:39:12: note: previous declaration of 'save_stack_trace_tsk_reliable' was here
extern int save_stack_trace_tsk_reliable(struct task_struct *tsk,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/stacktrace.h: In function 'save_stack_trace_tsk_reliable':
>> include/linux/stacktrace.h:65:10: error: 'ENOSYS' undeclared (first use in this function)
return -ENOSYS;
^~~~~~
include/linux/stacktrace.h:65:10: note: each undeclared identifier is reported only once for each function it appears in
make[2]: *** [kernel/bounds.s] Error 1
make[2]: Target '__build' not remade because of errors.
make[1]: *** [prepare0] Error 2
make[1]: Target 'prepare' not remade because of errors.
make: *** [sub-make] Error 2
vim +/ENOSYS +65 include/linux/stacktrace.h
60
61 #if !defined(CONFIG_STACKTRACE) || !defined(CONFIG_HAVE_RELIABLE_STACKTRACE)
> 62 static inline int save_stack_trace_tsk_reliable(struct task_struct *tsk,
63 struct stack_trace *trace)
64 {
> 65 return -ENOSYS;
66 }
67 #endif
68
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 27238 bytes --]
reply other threads:[~2019-04-16 10:12 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=201904161849.959pvukz%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tipbuild@zytor.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®