This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug uprobes/15315] New: Implement basic process filtering for inode-uprobes
- From: "jistone at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Wed, 27 Mar 2013 19:20:34 +0000
- Subject: [Bug uprobes/15315] New: Implement basic process filtering for inode-uprobes
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=15315
Bug #: 15315
Summary: Implement basic process filtering for inode-uprobes
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: uprobes
AssignedTo: systemtap@sourceware.org
ReportedBy: jistone@redhat.com
Blocks: 15278
Classification: Unclassified
When we use -c COMMAND, we expect process.* probes to only consider that
command and its children for probing, versus normally watching processes
system-wide.
However, that basic filtering is not fully implemented in the inode-uprobes
case. We do use task_finder2 to monitor only those child processes for
relevant binaries, but once registered we'll get events from that inode
system-wide.
For example:
$ stap -e 'global c; probe process("/lib64/libc.so.6").mark("*")
{ c[pid(), execname()] += 1 }' -c 'sleep 10'
c[2185,"gnome-shell"]=0x5a
c[28018,"sleep"]=0x1
The runtime internals should have skipped gnome-shell, as it's not a -c/-x
child.
This also triggers system-wide for --unprivileged, but that's ok security-wise
as long as the processes are still owned by the user. So if I add some root
activity while I run the same test, it does properly bail:
ERROR: Internal Error: Process 28926 does not belong to user 1000 in probe
process("/usr/lib64/libc-2.16.so").statement(0x311d635981) in --unprivileged
mode
Once we're properly tracking which processes we want, dynamically rejecting
unwanted processes from the handler, PR15278 prefiltering will probably be an
easy extension.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.