From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19791 invoked by alias); 18 Sep 2009 15:08:59 -0000 Received: (qmail 18506 invoked by uid 48); 18 Sep 2009 15:08:34 -0000 Date: Fri, 18 Sep 2009 15:08:00 -0000 Message-ID: <20090918150834.18505.qmail@sourceware.org> From: "mjw at redhat dot com" To: systemtap@sources.redhat.com In-Reply-To: <20090903122458.10595.mjw@redhat.com> References: <20090903122458.10595.mjw@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug uprobes/10595] uprobe probes causes selinux failures X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2009-q3/txt/msg00797.txt.bz2 ------- 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 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.