public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	2nddept-manager@sdl.hitachi.co.jp
Subject: Re: [PATCHv7 2.6.35-rc3-tip 0/11]  Uprobes Patches:
Date: Thu, 1 Jul 2010 11:58:15 +0200	[thread overview]
Message-ID: <20100701095815.GA26227@elte.hu> (raw)
In-Reply-To: <4C2C5D41.40807@hitachi.com>


* Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com> wrote:

> > - Plus the security model is an open question as well. Right now it's
> >   root-only, but it would make sense to allow users to insert probes into 
> >   their own apps. This brings up the next point:
> 
> Hmm, put a probe in user-space(by owner) may be good. But
> inside the kernel, there are more sensitive informations...

Yeah, clearly. Nevertheless this should not limit user-space probes.

	Ingo

      reply	other threads:[~2010-07-01  9:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-29 18:34 [PATCHv7 2.6.35-rc3-tip 0/11] Uprobes Patches: Srikar Dronamraju
2010-06-29 18:35 ` [PATCHv7 2.6.35-rc3-tip 1/11] mm: Move replace_page() / write_protect_page() to mm/memory.c Srikar Dronamraju
2010-06-29 18:35 ` [PATCHv7 2.6.35-rc3-tip 2/11] uprobes: Breakpoint insertion/removal in user space applications Srikar Dronamraju
2010-06-29 18:35 ` [PATCHv7 2.6.35-rc3-tip 3/11] uprobes: Slot allocation for Execution out of line(XOL) Srikar Dronamraju
2010-06-29 18:35 ` [PATCHv7 2.6.35-rc3-tip 4/11] uprobes: x86 specific functions for user space breakpointing Srikar Dronamraju
2010-06-29 18:35 ` [PATCHv7 2.6.35-rc3-tip 5/11] uprobes: Uprobes (un)registration and exception handling Srikar Dronamraju
2010-06-29 18:36 ` [PATCHv7 2.6.35-rc3-tip 6/11] uprobes: X86 support for Uprobes Srikar Dronamraju
2010-06-29 18:36 ` [PATCHv7 2.6.35-rc3-tip 7/11] uprobes: Uprobes Documentation Srikar Dronamraju
2010-06-29 18:36 ` [PATCHv7 2.6.35-rc3-tip 8/11] trace: Extract out common code for kprobes/uprobes traceevents Srikar Dronamraju
2010-06-29 18:36 ` [PATCHv7 2.6.35-rc3-tip 9/11] trace: uprobes trace_event interface Srikar Dronamraju
2010-06-29 18:36 ` [PATCHv7 2.6.35-rc3-tip 10/11] perf: Re-Add make_absolute_path Srikar Dronamraju
2010-06-29 18:37 ` [PATCHv7 2.6.35-rc3-tip 11/11] perf: perf interface for uprobes Srikar Dronamraju
2010-07-01  5:59   ` Masami Hiramatsu
2010-07-02 11:25     ` Masami Hiramatsu
2010-07-02 11:28       ` Srikar Dronamraju
2010-07-06  0:27         ` Masami Hiramatsu
2010-07-01  5:02 ` [PATCHv7 2.6.35-rc3-tip 0/11] Uprobes Patches: Srikar Dronamraju
2010-07-01  8:19   ` Ingo Molnar
2010-07-01  9:17     ` Masami Hiramatsu
2010-07-01  9:58       ` Ingo Molnar [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=20100701095815.GA26227@elte.hu \
    --to=mingo@elte.hu \
    --cc=2nddept-manager@sdl.hitachi.co.jp \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=rostedt@goodmis.org \
    --cc=srikar@linux.vnet.ibm.com \
    --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