From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9384 invoked by alias); 8 Apr 2008 14:13:06 -0000 Received: (qmail 9244 invoked by uid 48); 8 Apr 2008 14:12:21 -0000 Date: Tue, 08 Apr 2008 16:19:00 -0000 Message-ID: <20080408141221.9243.qmail@sourceware.org> From: "fche at redhat dot com" To: systemtap@sources.redhat.com In-Reply-To: <20080404085514.6030.ananth@in.ibm.com> References: <20080404085514.6030.ananth@in.ibm.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug runtime/6030] stap, staprun, stapio interaction quirks: stale module left unloaded X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2008-q2/txt/msg00032.txt.bz2 ------- Additional Comments From fche at redhat dot com 2008-04-08 14:12 ------- (In reply to comment #3) > cron wouldn't work well. If you wanted to run the same script you would > not be able to until cron had triggered the cleanup. As a user, I find > stuff like that extremely annoying. Remember, the scenario here is that the user killed his own stap* processes with kill -9. Such extreme annoyance is self-induced. I recall we came across some runes that perform pseudo-renaming of a compiled module before insmod time. If that can be made to work (as a part of staprun presumably), then reexecuting the same probe several times concurrently would be possible. Another simple possibility is for staprun to attempt to *unload* a module with the same name that it's about to load - to clean up an orphaned zombie. (It'd use sys_delete_module(2) with O_NONBLOCK.) > I still prefer the solution I described here > http://sources.redhat.com/bugzilla/show_bug.cgi?id=5716 > > "I think a simpler, more secure approach would be to simply separate the > module removal and build it as a standalone suid program. [...] Perhaps, but is it useful & necessary enough to overcome the natural skepticism toward adding anything setuid? -- 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.