Module unloading policy (should be killed from .config ?)

[J.A. Magallon]

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. If it is so dangerous and deprecated, why is still in Kconfig ?
Could you kill it and remove the code completely ? Because I suppose that
the idea is not to fix drivers...

But I guess this is going to break a lot of distros. At least Mandrake
initscripts is plenty of <modprobe, test, rmmod | modprobe -r> snippets.
Do not know if this is going to break cases like
modprobe -r xxxx || do_more

Could modprobe at least return 0 to the shell when removing ?

What is going on ?

TIA

--
J.A. Magallon <jamagallon()able!es>     \               Software is like sex:
werewolf!able!es                         \         It's better when it's free
Mandrakelinux release 10.1 (Beta 1) for i586
Linux 2.6.8.1-mm4 (gcc 3.4.1 (Mandrakelinux (Alpha 3.4.1-3mdk)) #8


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/