From owner-freebsd-hackers Mon Jan 8 18:24: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rjlhome.sco.com (unknown [207.65.180.181]) by hub.freebsd.org (Postfix) with ESMTP id 4E84937B402; Mon, 8 Jan 2001 18:23:46 -0800 (PST) Received: by rjlhome.sco.com (8.9.3/SCO5) id UAA10592; Mon, 8 Jan 2001 20:28:23 -0600 (CST) Date: Mon, 8 Jan 2001 20:28:23 -0600 From: Robert Lipe To: John Baldwin Cc: freebsd-hackers@FreeBSD.org Subject: Re: kthread_exit & zombification Message-ID: <20010108202823.A10376@rjlhome.sco.com> References: <20010108184732.N1400@rjlhome.sco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from jhb@FreeBSD.org on Mon, Jan 08, 2001 at 05:41:35PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > Unloading modules adds all sorts of new problems. Right now the WITNESS code > will do bad bad things if you kldunload a module that contains a mutex. Even > if the mutex is mtx_destroy'd because it still has a reference to its name in > the internal lists it keeps. Funny. I fixed a related problem in the UDI code just this morning. Those linked lists that walk into modules that have been unmapped can be a killer. :-) But this solves the problem I have right now. Thanx! > > to proc_reparent() and life seems pretty good. `ps' no longer panics > > and the lwp does indeed disappear from the ps listing instead of > > merely going zombie. This doesn't quite seem to jive with what you > > described above, though. > > By reparenting to init, the zombie is harvested isntead of lying > around. Now I just need to MFC this. Aaaah. Now I understand. Later, RJL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message