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


------- Additional Comments From fche at redhat dot com  2009-09-10 15:49 -------
I can't seem to reproduce this exactly on a pretty plain rawhide x86-64 box:

sudo ./stap -e 'probe process("./stap").function("*").return {}' -t -c './stap -V'
WARNING: u*probe failed stap[1567]
'process("/notnfs/BUILDg3/stap").function("~basic_stringbuf@/usr/lib/gcc/x86_64-redhat-linux/4.4.1/../../../../include/c++/4.4.1/iosfwd:63").return'
addr (null) rc -22
SystemTap translator/driver (version 0.9.9/0.142 commit release-0.9.9-278-ged4abdf)
Copyright (C) 2005-2009 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
WARNING: Number of errors: 0, skipped probes: 1
WARNING: Skipped due to uprobe register failure: 1
probe process("./stap").function("*").return (<input>:1:1), hits: 40, cycles:
440min/839avg/3192max

Note that we're registering 40 hits.

Linux vm-rawhide-64 2.6.31-0.204.rc9.fc12.x86_64 #1 SMP Sat Sep 5 20:45:55 EDT
2009 x86_64 x86_64 x86_64 GNU/Linux

[11:45:19] % getenforce 
Enforcing

[11:45:26] % getsebool -a | grep exec
allow_execheap --> off
allow_execmem --> off
allow_execmod --> off
allow_execstack --> off
allow_guest_exec_content --> off
allow_java_execstack --> off
allow_mplayer_execstack --> off
allow_nsplugin_execmem --> on
allow_staff_exec_content --> on
allow_sysadm_exec_content --> on
allow_user_exec_content --> on
allow_xguest_exec_content --> off
allow_xserver_execmem --> off
httpd_execmem --> off
httpd_ssi_exec --> off


But here comes dmesg:

Sep 10 11:44:23 vm-rawhide-64 setroubleshoot: SELinux is preventing stap from
changing a writable memory segment executable. For complete SELinux messages.
run sealert -l ceedcc9e-b241-4b91-8307-bda74d8c2048



-- 


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-10 15:50 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 [this message]
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
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=20090910154941.11653.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).