From: Dan Rosenberg <drosenberg@vsecurity.com>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Paul Menage <menage@google.com>, Li Zefan <lizf@cn.fujitsu.com>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, John Stultz <johnstul@us.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Switch proc interfaces in kernel/ to %pK
Date: Wed, 19 Jan 2011 10:04:51 -0500 [thread overview]
Message-ID: <1295449491.1806.13.camel@dan> (raw)
In-Reply-To: <4D363E92.2020602@hitachi.com>
On Wed, 2011-01-19 at 10:29 +0900, Masami Hiramatsu wrote:
> (2011/01/19 7:51), Dan Rosenberg wrote:
> > Switch users of %p in /proc interfaces in kernel/ to %pK, to allow
> > configuring the level of exposure of kernel pointers via the
> > kptr_restrict sysctl.
>
> This report_probe interface is at /sys/kernel/debug/kprobes/list.
> Is that policy applied to debugfs interface (for debug) too?
> # in that case, you might update ftrace and perf tracing interfaces...
>
There's no reason to not update ftrace and perf too, since I'd assume no
one is using debugging interfaces without root privileges anyway. I'll
add them to my list.
> > diff --git a/kernel/kprobes.c b/kernel/kprobes.c
> > index 7798181..2437ca4 100644
> > --- a/kernel/kprobes.c
> > +++ b/kernel/kprobes.c
> > @@ -2021,11 +2021,11 @@ static void __kprobes report_probe(struct seq_file *pi, struct kprobe *p,
> > kprobe_type = "k";
> >
> > if (sym)
> > - seq_printf(pi, "%p %s %s+0x%x %s ",
> > + seq_printf(pi, "%pK %s %s+0x%x %s ",
> > p->addr, kprobe_type, sym, offset,
> > (modname ? modname : " "));
> > else
> > - seq_printf(pi, "%p %s %p ",
> > + seq_printf(pi, "%pK %s %pK ",
> > p->addr, kprobe_type, p->addr);
> >
> > if (!pp)
>
>
> --
> Masami HIRAMATSU
> 2nd Dept. Linux Technology Center
> Hitachi, Ltd., Systems Development Laboratory
> E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2011-01-19 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 22:51 [PATCH] Switch proc interfaces in kernel/ to %pK Dan Rosenberg
2011-01-18 22:52 ` Alexey Dobriyan
2011-01-18 23:13 ` Dan Rosenberg
2011-01-18 22:52 ` Paul Menage
2011-01-19 1:29 ` Masami Hiramatsu
2011-01-19 15:04 ` Dan Rosenberg [this message]
2011-01-20 1:18 ` 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=1295449491.1806.13.camel@dan \
--to=drosenberg@vsecurity.com \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=menage@google.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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