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 47/47] kernel//trace/trace_stack.c:263:26: error: invalid use of undefined type 'struct stack_trace'
Date: Mon, 15 Apr 2019 05:52:31 +0800 [thread overview]
Message-ID: <201904150528.RG5qUBUG%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3877 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.core/stacktrace
head: 63c35ea6b829a0f98d307a8dec038095681ecd13
commit: 63c35ea6b829a0f98d307a8dec038095681ecd13 [47/47] x86/stacktrace: Use common infrastructure
config: i386-randconfig-x010-201915 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
git checkout 63c35ea6b829a0f98d307a8dec038095681ecd13
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
kernel//trace/trace_stack.c:24:17: error: static declaration of 'stack_trace_index' follows non-static declaration
static unsigned stack_trace_index[STACK_TRACE_ENTRIES];
^~~~~~~~~~~~~~~~~
In file included from kernel//trace/trace_stack.c:12:0:
include/linux/ftrace.h:248:17: note: previous declaration of 'stack_trace_index' was here
extern unsigned stack_trace_index[];
^~~~~~~~~~~~~~~~~
kernel//trace/trace_stack.c:27:22: error: static declaration of 'stack_trace_max_size' follows non-static declaration
static unsigned long stack_trace_max_size;
^~~~~~~~~~~~~~~~~~~~
In file included from kernel//trace/trace_stack.c:12:0:
include/linux/ftrace.h:250:22: note: previous declaration of 'stack_trace_max_size' was here
extern unsigned long stack_trace_max_size;
^~~~~~~~~~~~~~~~~~~~
kernel//trace/trace_stack.c:28:24: error: static declaration of 'stack_trace_max_lock' follows non-static declaration
static arch_spinlock_t stack_trace_max_lock =
^~~~~~~~~~~~~~~~~~~~
In file included from kernel//trace/trace_stack.c:12:0:
include/linux/ftrace.h:251:24: note: previous declaration of 'stack_trace_max_lock' was here
extern arch_spinlock_t stack_trace_max_lock;
^~~~~~~~~~~~~~~~~~~~
kernel//trace/trace_stack.c: In function '__next':
>> kernel//trace/trace_stack.c:263:26: error: invalid use of undefined type 'struct stack_trace'
if (n >= stack_trace_max.nr_entries)
^
kernel//trace/trace_stack.c: In function 't_show':
kernel//trace/trace_stack.c:327:22: error: invalid use of undefined type 'struct stack_trace'
stack_trace_max.nr_entries);
^
kernel//trace/trace_stack.c:337:26: error: invalid use of undefined type 'struct stack_trace'
if (i >= stack_trace_max.nr_entries)
^
kernel//trace/trace_stack.c:340:30: error: invalid use of undefined type 'struct stack_trace'
if (i + 1 == stack_trace_max.nr_entries)
^
vim +263 kernel//trace/trace_stack.c
e5a81b62 Steven Rostedt 2008-08-27 257
e5a81b62 Steven Rostedt 2008-08-27 258 static void *
2fc5f0cf Li Zefan 2009-08-17 259 __next(struct seq_file *m, loff_t *pos)
e5a81b62 Steven Rostedt 2008-08-27 260 {
2fc5f0cf Li Zefan 2009-08-17 261 long n = *pos - 1;
e5a81b62 Steven Rostedt 2008-08-27 262
4285f2fc Thomas Gleixner 2019-04-10 @263 if (n >= stack_trace_max.nr_entries)
e5a81b62 Steven Rostedt 2008-08-27 264 return NULL;
e5a81b62 Steven Rostedt 2008-08-27 265
2fc5f0cf Li Zefan 2009-08-17 266 m->private = (void *)n;
1b6cced6 Steven Rostedt 2008-08-29 267 return &m->private;
e5a81b62 Steven Rostedt 2008-08-27 268 }
e5a81b62 Steven Rostedt 2008-08-27 269
:::::: The code at line 263 was first introduced by commit
:::::: 4285f2fcef8001ead0f1c9315ba50302cab68cda tracing: Remove the ULONG_MAX stack trace hackery
:::::: TO: Thomas Gleixner <tglx@linutronix.de>
:::::: CC: Thomas Gleixner <tglx@linutronix.de>
---
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: 27248 bytes --]
reply other threads:[~2019-04-14 21:56 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=201904150528.RG5qUBUG%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 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.