kldunload DIAGNOSTIC idea...

[Poul-Henning Kamp]

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 at 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.