On 25-04-08 20:06, Robert P. J. Day wrote:
$ grep -rw MODULE_STACKSIZE * include/asm-x86/module.h:# define MODULE_STACKSIZE "4KSTACKS " include/asm-x86/module.h:# define MODULE_STACKSIZE "" include/asm-x86/module.h:# define MODULE_ARCH_VERMAGIC MODULE_PROC_FAMILY MODULE_STACKSIZE include/asm/module.h:# define MODULE_STACKSIZE "4KSTACKS " include/asm/module.h:# define MODULE_STACKSIZE "" include/asm/module.h:# define MODULE_ARCH_VERMAGIC MODULE_PROC_FAMILY MODULE_STACKSIZE i see a bunch of #defines, but no one using it for anything. am i missing something?
The last define is the important one. Try a "modinfo <module>" and see how "4KSTACKS" shows up alongside other flags in the version magic. 4KSTACKS is fundamental: if a module is compiled for 8K stacks and does esp & ~(8192-1) to get at thread_info, it's not going to find it there when running on a 4K stacks kernel as the most definite mismatch. This is why modprobe (without forcing it) would refuse to load the module.
Rene. -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
