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. -- dwmw2 - 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/
- Re: Linux 2.4 Status / TODO page (Updated... Jeff Garzik
- Re: Linux 2.4 Status / TODO page (Updated as of 2.... Philipp Rumpf
- Re: Linux 2.4 Status / TODO page (Updated as of 2.... James Simmons
- loop device hangs Christian van Enckevort
- Re: Linux 2.4 Status / TODO page (Updated as of 2.... Keith Owens
- Re: Linux 2.4 Status / TODO page (Updated as ... Russell King
- Re: Linux 2.4 Status / TODO page (Updated as ... David Woodhouse
- Re: Linux 2.4 Status / TODO page (Updated... Keith Owens
- Persistent module storage [was Linux ... David Woodhouse
- Persistent module storage [was Li... Keith Owens
- Re: Persistent module storag... David Woodhouse
- Re: Persistent module storag... Oliver Xymoron
- Re: Persistent module st... David Woodhouse
- Re: Persistent module st... Jeff Garzik
- Re: Persistent module st... David Woodhouse
- Re: Persistent module st... Alan Cox
- Re: Persistent module st... Dan Hollis
- Re: Persistent module st... Jeff Garzik
- Re: Persistent module st... Alan Cox