[Bug runtime/4357] New: staprun should print more obvious errors when not run as root

[Bug runtime/4357] New: staprun should print more obvious errors when not run as root

[fche at redhat dot com]

A user reports:

[eteo@kerndev ~]$ staprun ioblock.ko
insmod: error inserting 'ioblock.ko': -1 Operation not permitted
ERROR, couldn't insmod probe module ioblock.ko
Couldn't initialize staprun. Exiting.

It would be better if staprun produced fewer but higher-quality errors.
One way to do this would be to stop calling /sbin/insmod, and just call
the create_module(2) syscall.  If that returns EPERM, staprun can figure
out why it failed, and print just one salient line.

-- 
           Summary: staprun should print more obvious errors when not run as
                    root
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: fche at redhat dot com


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

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug runtime/4357] staprun should print more obvious errors when not run as root

[sarahgindin at gmail dot com]

------- Additional Comments From sarahgindin at gmail dot com  2007-05-06 17:39 -------
Created an attachment (id=1771)
 --> (http://sourceware.org/bugzilla/attachment.cgi?id=1771&action=view)
test


-- 


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

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Re: [Bug runtime/4357] staprun should print more obvious errors when not run as root

[Stone, Joshua I]

sarahgindin at gmail dot com wrote:
> ------- Additional Comments From sarahgindin at gmail dot com  2007-05-06 17:39 -------
> Created an attachment (id=1771)
>  --> (http://sourceware.org/bugzilla/attachment.cgi?id=1771&action=view)
> test

This is very clearly a spam attachment -- is this a legitimate "test" of 
the spam filtering?  I suspect not, and there's a similar attachment on 
bug #2033.  What is the proper bugzilla method for dealing with this?


Josh

Re: [Bug runtime/4357] staprun should print more obvious errors when not run as root

[Frank Ch. Eigler]

"Stone, Joshua I" <joshua.i.stone@intel.com> writes:

> This is very clearly a spam attachment -- is this a legitimate
> "test" of the spam filtering?  [...]  What is the proper bugzilla
> method for dealing with this?

Apparently there isn't one, short of low-level SQL manipulation
of the database.  ARGH.

- FChE

[Bug runtime/4357] staprun should print more obvious errors when not run as root

[dsmith at redhat dot com]

------- Additional Comments From dsmith at redhat dot com  2007-08-16 18:19 -------
With the new staprun security model (see bug 4523 for details), staprun no
longer requires root access.  However, you must be either root, a member of the
'stapdev' group, or a member of the 'stapusr' group to run staprun.

If you aren't root or a member of the 'stapdev' or 'stapusr' groups, then you
will get the following error message when starting staprun (in this example the
'news' user is used, which isn't a member of 'stapdev' or 'stapusr'):

$ sudo runuser -c "staprun stap_open.ko" news
ERROR: you must be a member of either group "stapdev" or group "stapusr"

staprun [-v]  [-c cmd ] [-x pid] [-u user]
        [-A|-L] [-b bufsize] [-o FILE] MODULE [module-options]
-v              Increase verbosity.
-c cmd          Command 'cmd' will be run and staprun will
                exit when it does.  The '_stp_target' variable
                will contain the pid for the command.
-x pid          Sets the '_stp_target' variable to pid.
-o FILE         Send output to FILE.
-b buffer size  The systemtap module specifies a buffer size.
                Setting one here will override that value.  The
                value should be an integer between 1 and 64
                which be assumed to be the buffer size in MB.
                That value will be per-cpu in bulk mode.
-L              Load module and start probes, then detach.
-A              Attach to loaded systemtap module.
MODULE can be either a module name or a module path.  If a
module name is used, it is looked for in the following
directory: /lib/modules/`uname -r`/systemtap

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED


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

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.