On Thu, 2003-07-24 at 19:00, Rusty Russell wrote:
> 	If module removal is to be a rare and unusual event, it
> doesn't seem so sensible to go to great lengths in the code to handle
> just that case.  In fact, it's easier to leave the module memory in
> place, and not have the concept of parts of the kernel text (and some
> types of kernel data) vanishing.

Wasn't the idea once banded about of a 2-stage unload that went
something like:

1. ->cleanup() - unregister IRQ handlers, timers, etc.
2. Quiesce the system
3. Safe to unload

surely if nothing is registered and all CPUs do a voluntary schedule()
then there can be no chance of calling back in to the module.

LOL. Or am I kidding myself here? :)

-- 
// Gianni Tedesco (gianni at scaramanga dot co dot uk)
lynx --source www.scaramanga.co.uk/gianni-at-ecsc.asc | gpg --import
8646BE7D: 6D9F 2287 870E A2C9 8F60 3A3C 91B5 7669 8646 BE7D