Re: Bug in kmem_cache_create with duplicate names

[Steven Rostedt <rostedt@goodmis.org>]

On Tue, 2004-12-07 at 11:15 -0500, Arjan van de Ven wrote:

> > However, I agree with you.  I don't see a good reason for it.
> 
> I do...
> because if the registration gives success..... then you unregister it
> later during module unload and the INITIAL user goes bang.
> It's a bad bug. Don't do it. Fix your code ;)
> 

Your module should fail to load if you can't register a cache. If you
are a good boy and check your return codes from the kmem_cache_create,
you would know that the cache failed and not load the module.
Otherwise, if it failed for other reasons, then you can be causing bugs
later when you go to use it. 

Now this raises the issue of name space, this will bug if two modules
use the same cache name. If this happens with two different vendors,
than the poor user will have to figure out who to blame.

-- Steve

(Arjan, Sorry for the duplicate, I forgot to do a reply all)