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: "mjw at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 18 Sep 2009 15:08:34 -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 mjw at redhat dot com 2009-09-18 15:08 -------
Neither the issue in comment #17 nor the issue in comment #18 could be reproduced.
There were two different issues though, neither apparently directly related to
this bug, but just with symptoms that looked similar.
1) The new enabled semaphores used the .probes section for holding variables.
This conflicted with the non-writable .probes section definition in sdt.h. This
was fixed by:
commit 5ee3f305e81fd2e1953d8a74530326f728a33ce8
Author: Mark Wielaard <mjw@redhat.com>
Date: Fri Sep 18 16:13:24 2009 +0200
Always mark .probes section as writable.
Allocated section needs to be writable when creating pic shared objects
because we store relocatable addresses in them. We used to make this
read only for non-pic executables, but the new semaphore support relies
on having a writable .probes section to put the enabled variables in.
* includes/sys/sdt.h (ALLOCSEC): Define unconditionally as "aw".
2) There seems to be a kernel warning (bug?) in ima_file_free() called by
selinux_file_free_security() that triggers with and without this fix.
https://bugzilla.redhat.com/show_bug.cgi?id=519737
--
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.