From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Bug in kmem_cache_create with duplicate names
Date: Tue, 07 Dec 2004 07:42:48 -0800 [thread overview]
Message-ID: <41B5CF78.4030206@osdl.org> (raw)
In-Reply-To: <1102436157.2882.8.camel@laptop.fenrus.org>
Arjan van de Ven wrote:
> On Tue, 2004-12-07 at 07:33 -0800, Randy.Dunlap wrote:
>
>>Steven Rostedt wrote:
>>
>>>Is it really necessary to BUG on creating a cache with a duplicate name?
>>>Wouldn't it just be better to fail the create. The reason I mentioned
>>>this is that I was writing some modules and after doing a cut and paste,
>>>I forgot to change a name of a cache that was created by one module and
>>>I used it in another existing module. So you can say that it was indeed
>>>a bug, but did it really need to crash my machine? I aways check the
>>>return codes in my modules, and I would have figured it out why it
>>>failed, but I didn't expect a simple module to crash the machine the way
>>>it did. Well anyway it did definitely show me where my bug was.
>>
>>Yes, it does that.
>>
>>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 ;)
Who said anything about the (second) registration giving success?
and how is it destroyed without a valid ptr to it?
--
~Randy
next prev parent reply other threads:[~2004-12-07 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 15:40 Bug in kmem_cache_create with duplicate names Steven Rostedt
2004-12-07 15:33 ` Randy.Dunlap
2004-12-07 16:15 ` Arjan van de Ven
2004-12-07 15:42 ` Randy.Dunlap [this message]
[not found] ` <1102436777.25841.271.camel@localhost.localdomain>
2004-12-07 16:31 ` Steven Rostedt
2004-12-07 17:57 ` Peter W. Morreale
2004-12-07 18:24 ` Steven Rostedt
2004-12-07 16:21 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41B5CF78.4030206@osdl.org \
--to=rddunlap@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox