Fails to run as unprivileged user
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemtap (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Originally posted to the systemtap mailing list: http://
I have a problem with running SystemTap as unprivileged user.
Executing the following probe as root works fine[0]:
stap -e 'probe vfs.read {printf("read performed\n"); exit()}'
However, running it as user (in 'stapusr' and stapdev' groups) fails[1]. Doing the same in Fedora 17 Alpha succeeds.
The module gets loaded, but 'stapio' is never run, and the removal of the module seems to fail as well, as it's still loaded when 'stap' exits.
All the suggested config options are set in the Ubuntu kernel[2] (except of CONFIG_UTRACE, though that's not necessary for that test I guess).
There are no dmesg errors (see working[3] and failing[4] -DDEBUG_TRANS output).
What I tried:
* A tailored 3.3-rc5 vanilla kernel with UTRACE patched in, same result.
* Disabled AppArmor, no joy.
* Tested the 3/3/2012 snapshot of SystemTap. That slightly changed the output but not the end result[5].
* Tested a vanilla 3.3-rc5 kernel with the Fedora 17 Alpha kernel config[6], which failed too.
Colin King's first idea: "I suspect it is some user space foo config that we're missing" - would be interesting to reveal that foo. :-)
0: Working as root: http://
1: Failing as user: http://
2: Ubuntu kernel config: http://
3: 1.6 dmesg working: http://
Snapshot dmesg working: http://
4: 1.6 dmesg failing: http://
Snapshot dmesg failing: http://
5: Ubuntu with snapshot: http://
6: Fedora kernel config: http://
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: systemtap (not installed)
ProcVersionSign
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Tue Mar 13 11:15:38 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
SourcePackage: systemtap
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in systemtap (Ubuntu): | |
status: | Fix Committed → Fix Released |
Just for the sake of completeness: this is still happening in the final release of Ubuntu 12.04.