[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1345856440.12440.21.camel@gandalf.local.home>
Date: Fri, 24 Aug 2012 21:00:40 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Wu Fengguang <fengguang.wu@...el.com>
Subject: Re: BUG: Kprobe smoke test: 2 out of 6 tests failed
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
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists