From: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Wu Fengguang <fengguang.wu@intel.com>
Subject: Re: BUG: Kprobe smoke test: 2 out of 6 tests failed
Date: Fri, 24 Aug 2012 21:00:40 -0400 [thread overview]
Message-ID: <1345856440.12440.21.camel@gandalf.local.home> (raw)
In-Reply-To: <1345815698.12440.12.camel@gandalf.local.home>
On Fri, 2012-08-24 at 09:41 -0400, Steven Rostedt wrote:
> On Fri, 2012-08-24 at 15:15 +0800, Fengguang Wu wrote:
> > Hi Steven,
> >
> > The following test fails are mostly due to this commit, or one of the
> > last 4 commits in
> >
> > tree: git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git tip/perf/core
> > head: d57c5d51a30152f3175d2344cb6395f08bf8ee0c
> > commit: d57c5d51a30152f3175d2344cb6395f08bf8ee0c [100/100] ftrace/x86: Add support for -mfentry to x86_64
> >
> > [ 9.084881] Kprobe smoke test failed: register_jprobe returned -22
> > [ 9.086786] Kprobe smoke test failed: register_jprobes returned -22
Masami,
Seems that when we use fentry, we break jprobes. I thought the patches
that we added would just move the call to the next op, not fail totally?
Are jprobes deprecated?
-- Steve
> > [ 9.121281] BUG: Kprobe smoke test: 2 out of 6 tests failed
> > [ 9.171132] Testing tracer function: PASSED
> > [ 9.408938] Testing dynamic ftrace: PASSED
> >
> > Thanks,
> > Fengguang
>
next prev parent reply other threads:[~2012-08-25 1:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 7:15 Fengguang Wu
2012-08-24 13:41 ` Steven Rostedt
2012-08-25 1:00 ` Steven Rostedt [this message]
2012-08-29 8:08 ` Masami Hiramatsu
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=1345856440.12440.21.camel@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.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
Powered by JetHome