Please cc me since I'm not on the mailing list.
While debugging several proprietary modules at work with a dual SMP x86
box running a 2.4.18 kernel, I noticed that when attempting to
concurrently execute two scripts that loaded and unloaded a stack of
modules, the box kept on crashing. In my search for the problem I noticed
that the function "sys_init_module" in kernel/module.c may have a
Assume that one script invokes modprobe which calls "sys_init_module"
first. The big kernel lock is taken and then plenty of sanity checks
done. After dependencies are checked and updated, the "init_module"
function of the module is invoked. Now if this function happens to block,
the kernel lock is dropped. A call to "sys_init_module" by modprobe in
the other script to initialise a second module dependent on the first
could then take the big kernel lock, check the dependencies and find them
okay, and then have its "init_module" function invoked. And if this
second module relies on the first module being properly initialised
before it is loaded, this can break.
Is this an issue that requires attention? Or am I overlooking something
in the code?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Aug 07 2002 - 22:00:26 EST