This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug runtime/15408] procfs probes broken on rawhide


http://sourceware.org/bugzilla/show_bug.cgi?id=15408

Josh Stone <jistone at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jistone at redhat dot com

--- Comment #8 from Josh Stone <jistone at redhat dot com> 2013-05-09 23:10:41 UTC ---
(In reply to comment #7)
> Fixed in commit be66b6e. Now creates top-level procfs directory during
> module_init() (when staprun is running), instead of during
> systemtap_module_init() (when stapio is running). When staprun is running, we
> have root access (euid == 0), since it is a setuid program.

This commit breaks RHEL4 support, so even the simplest script fails as:
> Error inserting module '[stap...].ko': Operation not permitted

The kernel log says:
> Systemtap Error at _stp_register_ctl_channel:597 Error creating systemtap control channel.

Then I looked and see /proc/systemtap/ is left there with a stap_...
subdirectory.  When I tried to read that, the kernel crashes from
proc_lookup().

IIRC, in RHEL4 we use procfs for transport (vs. debugfs everywhere else), so
perhaps that's conflicting with your change?  I'm quite sure though, reverting
just your commit clears it up.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]