Re: RFC - Approaches to user-space probes

[Arjan van de Ven <arjan@infradead.org>]

On Mon, 2006-03-27 at 15:30 +0530, Prasanna S Panchamukhi wrote:
> On Mon, Mar 27, 2006 at 09:37:48AM +0200, Arjan van de Ven wrote:
> > On Mon, 2006-03-27 at 12:24 +0530, Prasanna S Panchamukhi wrote:
> > 
> > > - Low overhead and user can have thousands of active probes on the
> > >   system and detect any instance when the probe was hit including
> > >   probes on shared library etc.
> > 
> > I suspect this is the only reason for doing it inside the kernel;
> > anything else still really shouts "do it in userspace via ptrace" to me.
> > 
> 
> Other reasons would be:
> 
> - to view some privilaged data, such as system regs while you are
>   debugging in user-space

root can do that anyway afaics

> - to view many arbitrary process address-space that use a common set
>   of modules - user or kernel space

that's just a matter of userspace tooling.

> Yes, insertion of the breakpoint happens at the physical
> page level and it gets written back to the disc.

at which point you get to deal with tripwire and other intrusion
detection systems.... and you prevent doing this on binaries residing on
read-only mounts (which isn't as uncommon as it sounds, read only
shared /usr is quite common in enterprise)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/