All of lore.kernel.org
 help / color / mirror / Atom feed
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 18/47] kernel//trace/trace_stack.c:24:17: error: static declaration of 'stack_trace_index' follows non-static declaration
Date: Mon, 15 Apr 2019 05:42:13 +0800	[thread overview]
Message-ID: <201904150510.977CDVul%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2774 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.core/stacktrace
head:   63c35ea6b829a0f98d307a8dec038095681ecd13
commit: 4a934c54305ab50cf2d4b0afb915feee0dbb487e [18/47] tracing: Cleanup stack trace code
config: i386-randconfig-x010-201915 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
        git checkout 4a934c54305ab50cf2d4b0afb915feee0dbb487e
        # 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:36: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:37: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;
                           ^~~~~~~~~~~~~~~~~~~~

vim +/stack_trace_index +24 kernel//trace/trace_stack.c

    22	
    23	static unsigned long stack_dump_trace[STACK_TRACE_ENTRIES];
  > 24	static unsigned stack_trace_index[STACK_TRACE_ENTRIES];
    25	
    26	/*
    27	 * Reserve one entry for the passed in ip. This will allow
    28	 * us to remove most or all of the stack size overhead
    29	 * added by the stack tracer itself.
    30	 */
    31	struct stack_trace stack_trace_max = {
    32		.max_entries		= STACK_TRACE_ENTRIES - 1,
    33		.entries		= &stack_dump_trace[0],
    34	};
    35	
  > 36	static unsigned long stack_trace_max_size;
  > 37	static arch_spinlock_t stack_trace_max_lock =
    38		(arch_spinlock_t)__ARCH_SPIN_LOCK_UNLOCKED;
    39	

---
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: 27237 bytes --]

                 reply	other threads:[~2019-04-14 21:43 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=201904150510.977CDVul%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.