Date: Tue, 20 Jul 2004 20:20:23 +0200 From: Poul-Henning Kamp <phk@phk.freebsd.dk> To: arch@freebsd.org Subject: kldunload DIAGNOSTIC idea... Message-ID: <75243.1090347623@critter.freebsd.dk>
next in thread | raw e-mail | index | archive | help
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 ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?75243.1090347623>