Re: pre-patch-2.1.107 breaks kmod
H. Peter Anvin (hpa@transmeta.com)
Fri, 26 Jun 1998 00:15:47 -0700 (PDT)
> OK. I understand now. I guess Peter's suggestion of
> having insmod use flock to achieve this would be a servicible
> approach. However, there seem to be a lot of "activated states"
> in the process of loading a module (the module is registered but not
> loaded, the lock on the module file has been acquired, what if
> there are two copies of the same module .o file?, etc.). Is there
> some reason why create_module() is a separate system call from
> init_module? It seems to me that you could avoid creating these
> locking conventions that everyone would have to think about by making
> create_module() a no-op and making init_module() atomically do the
> job of create_module+init_module.
Yes, you need to reserve kernel memory in advance since the relocation
occurs in user space (as it should.)
-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu