This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug uprobes/10595] uprobe probes causes selinux failures
- From: "jkenisto at us dot ibm dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 3 Sep 2009 17:43:58 -0000
- Subject: [Bug uprobes/10595] uprobe probes causes selinux failures
- References: <20090903122458.10595.mjw@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From jkenisto at us dot ibm dot com 2009-09-03 17:43 -------
(In reply to comment #2)
> It isn't return probe specific like I first thought.
> With both normal and return probes there is this hint in /var/log/messages:
> kernel: Uprobes failed to allocate a vma for pid/tgid 17519/17519 for
> single-stepping out of line.
>
> The strange thing is that normal uprobes still seem to work, they trigger their
> handler as expected even though you get a selinux denial message, but return
> probes don't trigger.
When uprobes fails to create the vma, it falls back to single-stepping inline,
which doesn't require the vma. We don't have a Plan B for uretprobes, though:
the only place we know to put the uretprobe trampoline is in slot 0 of our vma
(There are, of course, alternatives, but they're not currently coded for.)
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10595
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.