From: Ingo Molnar <mingo@kernel.org>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Pratyush Anand <panand@redhat.com>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>, Rob Landley <rob@landley.net>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH tip/master 1/3] kprobes: Support blacklist functions in module
Date: Fri, 17 Jul 2015 14:10:37 +0200 [thread overview]
Message-ID: <20150717121037.GA9437@gmail.com> (raw)
In-Reply-To: <20150716071055.14218.64129.stgit@localhost.localdomain>
* Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com> wrote:
> To blacklist the functions in a module (e.g. user-defined
> kprobe handler and the functions invoked from it), expand
> blacklist support for modules.
> With this change, users can use NOKPROBE_SYMBOL() macro in
> their own modules.
Btw., whatever happened with renaming '__kprobes' to '__nokprobe' and using that
consistently to blacklist certain functions?
Also, shouldn't we convert such instances:
static int notifier_call_chain(struct notifier_block **nl,
unsigned long val, void *v,
int nr_to_call, int *nr_calls)
...
NOKPROBE_SYMBOL(notifier_call_chain);
to:
static int __nokprobe notifier_call_chain(struct notifier_block **nl,
unsigned long val, void *v,
int nr_to_call, int *nr_calls)
?
I.e. instead of extending it to modules we should eliminate NOKPROBE_SYMBOL() in
favor of marking functions as __nokprobe which is the standard syntax for marking
functions.
Thanks,
Ingo
next prev parent reply other threads:[~2015-07-17 12:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 7:10 [PATCH tip/master 0/3] kprobes blacklist enhancement Masami Hiramatsu
2015-07-16 7:10 ` [PATCH tip/master 1/3] kprobes: Support blacklist functions in module Masami Hiramatsu
2015-07-16 11:34 ` Rusty Russell
2015-07-17 12:10 ` Ingo Molnar [this message]
2015-07-19 3:15 ` Masami Hiramatsu
2015-07-21 7:48 ` Ingo Molnar
2015-07-21 10:19 ` Masami Hiramatsu
2015-07-16 7:10 ` [PATCH tip/master 2/3] kprobes: Use NOKPROBE_SYMBOL() in sample modules Masami Hiramatsu
2015-07-16 7:10 ` [PATCH tip/master 3/3] kprobes/x86: Use kprobe_blacklist for .kprobes.text and .entry.text 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=20150717121037.GA9437@gmail.com \
--to=mingo@kernel.org \
--cc=ananth@in.ibm.com \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@redhat.com \
--cc=panand@redhat.com \
--cc=rob@landley.net \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
/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