From: John L. <mo...@co...> - 2001-09-02 01:01:40
|
We have to disable module unloading for each release I think. Whilst the race window between the incl of the module use count and user processes actually leaving the module code area is small, I don't think we can take the risk of leaving it in. Also as far as I understand we could be in much deeper trouble when the kernel becomes pre-emptible in 2.5. A silver bullet would be nice, but syscall intercepting is such an ugly thing to do, we will have to just accept one of its disadvantages. regards john -- "Do you mean to tell me that "The Prince" is not the set textbook for CS1072 Professional Issues ? What on earth do you learn in that course ?" - David Lester |