This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/6030] stap, staprun, stapio interaction quirks: stale module left unloaded
- From: "ananth at in dot ibm dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 8 Apr 2008 12:57:37 -0000
- Subject: [Bug runtime/6030] stap, staprun, stapio interaction quirks: stale module left unloaded
- References: <20080404085514.6030.ananth@in.ibm.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From ananth at in dot ibm dot com 2008-04-08 12:57 -------
Subject: Re: stap, staprun, stapio interaction quirks:
stale module left unloaded
On Fri, Apr 04, 2008 at 03:43:15PM -0000, hunt at redhat dot com wrote:
>
> "I think a simpler, more secure approach would be to simply separate the
> module removal and build it as a standalone suid program. It would
> check the user was in stapusr or stapdev, verify the module that was
> requested to be unloaded was a systemtap module, then unload it. That
> allows staprun to do some quick setup, load the module, then drop all
> capabilities (if we use them), fork stapio, and exit. Stapio would exec
> the module unloader when it got ^C or an exit message from the module."
>
> So staprun goes away and cannot be killed. SIGKILL on stapio would still
> leave the module installed, of course. So then you would run the
> unloader by hand. What would we call it? staprm? Or it could just be
> staprun with a flag to unload instead of load.
Yes, this sounds like a simpler solution.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=6030
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.