From: Andrew Morton <akpm@digeo.com>
To: Steve French <smfrench@austin.rr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: duplicate entry check in kmem_cache_create
Date: Wed, 18 Jun 2003 16:46:11 -0700 [thread overview]
Message-ID: <20030618164611.41ea172d.akpm@digeo.com> (raw)
In-Reply-To: <3EF0F0D5.5030504@austin.rr.com>
Steve French <smfrench@austin.rr.com> wrote:
>
> Is there a recommended way to check to see if a slab cache with
> a specific name exists before calling kmem_cache_create?
>
> I was able to force it into the BUG() at about line 1160 of slab.c by
> removing my
> module (rmmod -f) while some of my slab cache objects (e.g. private inode
> info) were still in use, and then reloading my module which called
> kmem_cache_create with a name that already existed.
errr, why on earth was the filesystem unloadable when it still had live
objects floating about?
At the very least, if the slab code tries to call a destructor it will ruin
your whole day.
next prev parent reply other threads:[~2003-06-18 23:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 23:08 duplicate entry check in kmem_cache_create Steve French
2003-06-18 23:46 ` Andrew Morton [this message]
2003-06-19 0:08 ` Steve French
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=20030618164611.41ea172d.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=smfrench@austin.rr.com \
/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