mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: linux-kernel@vger.kernel.org
Cc: jmerkey@timpanogas.org
Subject: Re: BUG() at line 804, slab.c, 2.4.3
Date: Tue, 17 Apr 2001 15:52:54 -0600	[thread overview]
Message-ID: <20010417155254.A344@vger.timpanogas.org> (raw)
In-Reply-To: <20010417152920.A32576@vger.timpanogas.org>
In-Reply-To: <20010417152920.A32576@vger.timpanogas.org>; from jmerkey@vger.timpanogas.org on Tue, Apr 17, 2001 at 03:29:20PM -0600

On Tue, Apr 17, 2001 at 03:29:20PM -0600, Jeff V. Merkey wrote:

Added kmem_cache_destroy() to get around the problem.  I'm still
curious as to why we need to panic at this point rather than return
an error.  

Thanks

Jeff

> 
> 
> I noticed that subsequent calls to kmem_cache_create with the same name
> does not return an -EEXIST return code, but instead barfs and crashes
> with a bug at slab.c line 804.  This occurs in 2.4.3.
> 
> Is this the expected behavior for kmem_cache_create?  I am using 
> the slab allocator to create and maintain buffer head chains for 
> asynch I/O.
>  
> I would assume that if a valid tag existed, an error would be returned 
> rather than the system crashing.   I see the problem unloading then 
> reloading the module on 2.4.3.  
> 
> Thanks,
> 
> Jeff
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

      reply	other threads:[~2001-04-17 21:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-17 21:29 Jeff V. Merkey
2001-04-17 21:52 ` Jeff V. Merkey [this message]

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=20010417155254.A344@vger.timpanogas.org \
    --to=jmerkey@vger.timpanogas.org \
    --cc=jmerkey@timpanogas.org \
    --cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®