From: Ingo Molnar <mingo@kernel.org>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: "Steven Rostedt" <rostedt@goodmis.org>,
"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:07:37 +0100 [thread overview]
Message-ID: <20131106060737.GC24044@gmail.com> (raw)
In-Reply-To: <5278D89B.1070806@hitachi.com>
* Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com> wrote:
> >> [...] I hope to build the list when the kernel build time if
> >> possible... Would you have any idea to classify some annotated(but no
> >> side-effect) functions?
> >
> > The macro magic I can think of would need to change the syntax of the
> > function definition - for example that is how the SYSCALL_DEFINE*()
> > macros work.
>
> Would you mean something like the below macro? :)
>
> NOKPROBE_SYMBOL(int, func_ptr_is_kernel_text)(void *ptr)
I think this is rather ugly and harder to maintain. The whole _point_ of
such annotations is to make them 'easy on the eyes', to make it easy to
skip a 'noinline', 'noprobe' or 'notrace' tag.
Using something like NOKPROBE_SYMBOL() makes the whole construct ugly and
attention seeking.
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.
Thanks,
Ingo
next prev parent reply other threads:[~2013-11-06 6:07 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 [this message]
2013-11-06 10:34 ` Masami Hiramatsu
2013-11-06 11:50 ` Ingo Molnar
2013-11-06 12:21 ` Steven Rostedt
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=20131106060737.GC24044@gmail.com \
--to=mingo@kernel.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=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.