public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug uprobes/10595] uprobe probes causes selinux failures
Date: Fri, 18 Sep 2009 15:08:00 -0000	[thread overview]
Message-ID: <20090918150834.18505.qmail@sourceware.org> (raw)
In-Reply-To: <20090903122458.10595.mjw@redhat.com>


------- 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.

  parent reply	other threads:[~2009-09-18 15:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-03 12:25 [Bug uprobes/10595] New: uprobe return " mjw at redhat dot com
2009-09-03 14:18 ` [Bug uprobes/10595] " mjw at redhat dot com
2009-09-03 16:25 ` [Bug uprobes/10595] uprobe " mjw at redhat dot com
2009-09-03 17:44 ` jkenisto at us dot ibm dot com
2009-09-03 20:13 ` mjw at redhat dot com
2009-09-04 11:09 ` mjw at redhat dot com
2009-09-04 11:58 ` srikar at linux dot vnet dot ibm dot com
2009-09-04 17:11 ` jkenisto at us dot ibm dot com
2009-09-04 17:25 ` mjw at redhat dot com
2009-09-04 18:08 ` jkenisto at us dot ibm dot com
2009-09-07 11:38 ` mjw at redhat dot com
2009-09-08 12:26 ` srikar at linux dot vnet dot ibm dot com
2009-09-10 15:50 ` fche at redhat dot com
2009-09-14 18:51 ` fche at redhat dot com
2009-09-14 19:27 ` mjw at redhat dot com
2009-09-14 19:51 ` mjw at redhat dot com
2009-09-17 10:27 ` mjw at redhat dot com
2009-09-17 13:14 ` mjw at redhat dot com
2009-09-17 15:53 ` fche at redhat dot com
2009-09-18 15:08 ` mjw at redhat dot com [this message]
2009-12-14 14:19 ` mjw at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090918150834.18505.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).