From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: include/linux/kprobes.h:361:2: error: invalid use of undefined type 'struct kprobe_ctlblk'
Date: Sun, 13 Mar 2016 16:00:16 +0000 [thread overview]
Message-ID: <20160313160016.GS19428@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <201603131629.FpeiMSQK%fengguang.wu@intel.com>
On Sun, Mar 13, 2016 at 04:37:14PM +0800, kbuild test robot wrote:
> Hi Russell,
>
> FYI, the error/warning still remains.
Sorry, I've no clue about this. From what I can see, kprobes.h is
correct.
#ifdef CONFIG_KPROBES
DECLARE_PER_CPU(struct kprobe *, current_kprobe);
DECLARE_PER_CPU(struct kprobe_ctlblk, kprobe_ctlblk);
...
static inline struct kprobe_ctlblk *get_kprobe_ctlblk(void)
{
return this_cpu_ptr(&kprobe_ctlblk);
}
The only way I can see that kprobe_ctlblk would be undefined is if
MN10300 were doing something totally weird with DECLARE_PER_CPU().
Since I know precisely nothing about MN10300, and it doesn't seem to
touch the definition of DECLARE_PER_CPU(), I'm at a total loss to
understand how this error can occur.
Some help would be nice - as right now I have absolutely no idea on
this.
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-03-13 16:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 8:37 include/linux/kprobes.h:361:2: error: invalid use of undefined type 'struct kprobe_ctlblk' kbuild test robot
2016-03-13 16:00 ` Russell King - ARM Linux [this message]
-- 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=20160313160016.GS19428@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--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).