mirror of https://lore.kernel.org/lkml/
 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 32/32] include/linux/stacktrace.h:84:14: warning: 'struct stack_trace' declared inside parameter list
Date: Tue, 16 Apr 2019 18:12:42 +0800	[thread overview]
Message-ID: <201904161835.Jpd9ydho%lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.core/stacktrace
head:   9fe290aca53f59fd24187841dd4a8ff41ade91bd
commit: 9fe290aca53f59fd24187841dd4a8ff41ade91bd [32/32] x86/stacktrace: Use common infrastructure
config: i386-randconfig-a1-201915 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
        git checkout 9fe290aca53f59fd24187841dd4a8ff41ade91bd
        # save the attached .config to linux build tree
        make ARCH=i386 

All warnings (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:84:14: warning: 'struct stack_trace' declared inside parameter list
          struct stack_trace *trace)
                 ^
>> include/linux/stacktrace.h:84:14: warning: its scope is only this definition or declaration, which is probably not what you want
   include/linux/stacktrace.h: In function 'save_stack_trace_tsk_reliable':
   include/linux/stacktrace.h:86:10: error: 'ENOSYS' undeclared (first use in this function)
     return -ENOSYS;
             ^
   include/linux/stacktrace.h:86: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 +84 include/linux/stacktrace.h

8637c099 Ingo Molnar     2006-07-03  81  
714f46ba Thomas Gleixner 2019-04-09  82  #if !defined(CONFIG_STACKTRACE) || !defined(CONFIG_HAVE_RELIABLE_STACKTRACE)
714f46ba Thomas Gleixner 2019-04-09  83  static inline int save_stack_trace_tsk_reliable(struct task_struct *tsk,
714f46ba Thomas Gleixner 2019-04-09 @84  						struct stack_trace *trace)
714f46ba Thomas Gleixner 2019-04-09  85  {
714f46ba Thomas Gleixner 2019-04-09  86  	return -ENOSYS;
714f46ba Thomas Gleixner 2019-04-09  87  }
714f46ba Thomas Gleixner 2019-04-09  88  #endif
714f46ba Thomas Gleixner 2019-04-09  89  

:::::: The code at line 84 was first introduced by commit
:::::: 714f46ba649b163e80d3dd89e83b92f4ba5ac6af stacktrace: Provide helpers for common stack trace operations

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

                 reply	other threads:[~2019-04-16 10:13 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=201904161835.Jpd9ydho%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®