Date: Tue, 20 Jul 2004 14:32:13 -0400 From: Brian Fundakowski Feldman <green@freebsd.org> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: arch@freebsd.org Subject: Re: kldunload DIAGNOSTIC idea... Message-ID: <20040720183213.GC1009@green.homeunix.org> In-Reply-To: <75243.1090347623@critter.freebsd.dk> References: <75243.1090347623@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 20, 2004 at 08:20:23PM +0200, Poul-Henning Kamp wrote: > > I'm pulling hair out trying to make it guaranteed safe to unload device > driver modules, and the major pain here is to make sure there is no > thread stuck somewhere inside the code. > > That gave me the idea for a simple little DIAGNOSTIC check for kldunload: > run through the proc/thread table and look for any thread with an > instruction counter inside the range of pages we are going to unload. > > Any takers ? You mean any thread with a stack trace that includes an instruction counter inside those pages, don't you? -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040720183213.GC1009>