From: kbuild test robot <fengguang.wu@intel.com>
To: Russell King <rmk+kernel@arm.linux.org.uk>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: include/linux/kprobes.h:361:2: error: invalid use of undefined type 'struct kprobe_ctlblk'
Date: Sun, 13 Mar 2016 16:37:14 +0800 [thread overview]
Message-ID: <201603131629.FpeiMSQK%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2131 bytes --]
Hi Russell,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: f414ca64be4b36c30deb5b5fa25c5a8ff42ea56b
commit: b2c0b2cbb282f0cf42518ffacbe197e6f2884168 nmi: create generic NMI backtrace implementation
date: 8 months ago
config: mn10300-allmodconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout b2c0b2cbb282f0cf42518ffacbe197e6f2884168
# save the attached .config to linux build tree
make.cross ARCH=mn10300
All errors (new ones prefixed by >>):
In file included from lib/nmi_backtrace.c:17:0:
include/linux/kprobes.h: In function 'get_kprobe_ctlblk':
>> include/linux/kprobes.h:361:2: error: invalid use of undefined type 'struct kprobe_ctlblk'
return this_cpu_ptr(&kprobe_ctlblk);
^
vim +361 include/linux/kprobes.h
e6584523 Ananth N Mavinakayanahalli 2005-11-07 355 {
b76834bc Christoph Lameter 2010-12-06 356 __this_cpu_write(current_kprobe, NULL);
e6584523 Ananth N Mavinakayanahalli 2005-11-07 357 }
e6584523 Ananth N Mavinakayanahalli 2005-11-07 358
e6584523 Ananth N Mavinakayanahalli 2005-11-07 359 static inline struct kprobe_ctlblk *get_kprobe_ctlblk(void)
e6584523 Ananth N Mavinakayanahalli 2005-11-07 360 {
bdffd893 Christoph Lameter 2014-04-29 @361 return this_cpu_ptr(&kprobe_ctlblk);
e6584523 Ananth N Mavinakayanahalli 2005-11-07 362 }
e6584523 Ananth N Mavinakayanahalli 2005-11-07 363
^1da177e Linus Torvalds 2005-04-16 364 int register_kprobe(struct kprobe *p);
:::::: The code at line 361 was first introduced by commit
:::::: bdffd893a0e9c431304142d12d9a0a21d365c502 tracing: Replace __get_cpu_var uses with this_cpu_ptr
:::::: TO: Christoph Lameter <cl@linux.com>
:::::: CC: Steven Rostedt <rostedt@goodmis.org>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 34526 bytes --]
next reply other threads:[~2016-03-13 8:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 8:37 kbuild test robot [this message]
2016-03-13 16:00 ` include/linux/kprobes.h:361:2: error: invalid use of undefined type 'struct kprobe_ctlblk' Russell King - ARM Linux
-- strict thread matches above, loose matches on Subject: below --
2017-02-12 7:41 kbuild test robot
2017-02-12 8:31 ` Russell King - ARM Linux
2016-11-13 1:09 kbuild test robot
2016-11-13 9:01 ` Russell King - ARM Linux
2016-10-02 1:31 kbuild test robot
2016-09-22 8:45 kbuild test robot
2016-03-06 3:53 kbuild test robot
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=201603131629.FpeiMSQK%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).