From: Steven Rostedt <rostedt@goodmis.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: "Masami Hiramatsu" <masami.hiramatsu.pt@hitachi.com>,
"Ananth N Mavinakayanahalli" <ananth@in.ibm.com>,
x86@kernel.org, lkml <linux-kernel@vger.kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Borislav Petkov" <bp@suse.de>
Subject: Re: [PATCH -tip v2 3/3] [BUGFIX] kprobes: Prohibit probing on func_ptr_is_kernel_text
Date: Wed, 6 Nov 2013 07:21:09 -0500 [thread overview]
Message-ID: <20131106072109.28fcb8ca@gandalf.local.home> (raw)
In-Reply-To: <20131106060737.GC24044@gmail.com>
On Wed, 6 Nov 2013 07:07:37 +0100
Ingo Molnar <mingo@kernel.org> wrote:
> So until compilers get smarter (or there's some compiler trick I haven't
> noticed) lets stay with the separate section - it's not the end of the
> world, the (effective) 'noinline' aspect of noprobes changes code
> generation anyway.
>
It's fine now. I just wanted everyone to be ware if this annotation
starts to get used a bit more, that it can cause unwanted side effects.
-- Steve
next prev parent reply other threads:[~2013-11-06 12:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 11:25 [PATCH -tip v2 0/3] kprobes: introduce nokprobe and updating blacklist Masami Hiramatsu
2013-11-01 11:25 ` [PATCH -tip v2 1/3] kprobes: Introduce nokprobe annotation for non-probe-able functions Masami Hiramatsu
2013-11-01 13:55 ` Steven Rostedt
2013-11-05 1:45 ` Masami Hiramatsu
2013-11-01 11:25 ` [PATCH -tip v2 2/3] [BUGFIX] kprobes/x86: Prohibit probing on debug_stack_* Masami Hiramatsu
2013-11-01 13:56 ` Steven Rostedt
2013-11-01 11:25 ` [PATCH -tip v2 3/3] [BUGFIX] kprobes: Prohibit probing on func_ptr_is_kernel_text Masami Hiramatsu
2013-11-01 13:57 ` Steven Rostedt
2013-11-05 2:00 ` Steven Rostedt
2013-11-05 3:15 ` Masami Hiramatsu
2013-11-05 6:09 ` Ingo Molnar
2013-11-05 6:59 ` Masami Hiramatsu
2013-11-05 7:05 ` Ingo Molnar
2013-11-05 11:38 ` Masami Hiramatsu
2013-11-05 12:35 ` Masami Hiramatsu
2013-11-06 6:07 ` Ingo Molnar
2013-11-06 10:34 ` Masami Hiramatsu
2013-11-06 11:50 ` Ingo Molnar
2013-11-06 12:21 ` Steven Rostedt [this message]
2013-11-05 13:13 ` Steven Rostedt
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=20131106072109.28fcb8ca@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®