Messages in this thread | | | Date | Thu, 2 Sep 2004 00:23:25 +0100 | From | Dave Jones <> | Subject | Re: Module unloading policy (should be killed from .config ?) |
| |
On Wed, Sep 01, 2004 at 10:59:57PM +0000, J.A. Magallon wrote: > Hi all... > > Since 2.6.8.1-mm3, my system hangs when I modprobe -r ipt_MASQUERADE > (yup, you guessed, its an SMP box). Just locks hard. > > A kernel build without module unloading seems to work. I heard about > module unloading not being safe, but this is the first time it hits me > seriously.
I wrote a script a while ago that modprobe'd & rmmod'd every module it could find. Results weren't pretty.
Lessons learned: - lots of driver writers don't take into consideration the fact the hardware might not be present when the driver does probing. - Those that do, fail to clean up properly in this case. - A lot of drivers leave junk in sysfs/procfs after rmmod which causes great fun for the next driver that gets loaded that uses the same subsystems.
It's been a few months since I last ran that script, but I'll bet the results today aren't much better than they were back then despite a bunch of problems I reported getting fixed.
Dave
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |