On Mon, 6 Nov 2000 00:54:51 +0000 (GMT),
David Woodhouse <[EMAIL PROTECTED]> wrote:
>On Mon, 6 Nov 2000, Keith Owens wrote:
>
>> I'm not sure why you think this can be used for module persistent
>> storage. If a module calls inter_module_register() on load, it should
>> call inter_module_unregister() on unload. All the registered data
>> points into the loaded module, remove the module and the storage
>> disappears as well.
>
>You can kmalloc() both the im_name and userdata arguments to
>inter_module_register and you ought to be able to pass NULL as the owner.
Ughh! That is definitely abusing the inter_module functions. If we
need persistent module storage then we should add a clean interface to
do it instead of using kmalloc and overloading inter_module_xxx.
What do people think, do we need module persistent storage? There are
already entries in struct module for persistent data but there is no
way of setting those fields, nor is there any code in modutils to
handle persistent storage. This will probably be a 2.5 change but I
want to get an idea of the requirements before coding anything.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
