From: Andrew Morton <akpm@linux-foundation.org>
To: Prashanth Nageshappa <prashanth@linux.vnet.ibm.com>
Cc: masami.hiramatsu.pt@hitachi.com, ananth@in.ibm.com,
linux-kernel@vger.kernel.org, jbaron@redhat.com,
rostedt@goodmis.org, srikar@linux.vnet.ibm.com,
stable@vger.kernel.org
Subject: Re: [PATCH v2] Return proper error code from register_kprobe()
Date: Wed, 15 Feb 2012 13:23:10 -0800 [thread overview]
Message-ID: <20120215132310.21c0dc77.akpm@linux-foundation.org> (raw)
In-Reply-To: <4F3B5BB3.9030907@linux.vnet.ibm.com>
On Wed, 15 Feb 2012 12:46:03 +0530
Prashanth Nageshappa <prashanth@linux.vnet.ibm.com> wrote:
> register_kprobe() aborts if the address of the new request falls in a
> prohibited area (such as ftrace pouch, __kprobes annotated functions,
I'm sitting here wondering what you meant to type when you typed
"ftrace pouch". I'm stumped! But you're not allowed to tell us - that
would take all the fun out of it.
> non-kernel text addresses, jump label text). We however don't return the
> right error on this abort, resulting in a silent failure - incorrect
> adding/reporting of kprobes ('perf probe do_fork+18' or
> 'perf probe mcount' for instance).
>
> In V2 we are incorporating Masami Hiramatsu's feedback.
>
> This patch fixes it by returning -EINVAL upon failure.
>
> While we are here, rename the label used for exit to be more appropriate.
>
> Signed-off-by: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
> Signed-off-by: Prashanth K Nageshappa <prashanth@linux.vnet.ibm.com>
> Cc: stable@vger.kernel.org
So we want this for 3.3 with a -stable backport.
prev parent reply other threads:[~2012-02-15 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 7:16 [PATCH v2] Return proper error code from register_kprobe() Prashanth Nageshappa
2012-02-15 21:23 ` Andrew Morton [this message]
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=20120215132310.21c0dc77.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=prashanth@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=stable@vger.kernel.org \
/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