From: Andrew Morton <akpm@zip.com.au>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: gregor@suhr.home.cs.tu-berlin.de, linux-kernel@vger.kernel.org
Subject: Re: OOPS at boot in 2.4.17-rc[12] (kernel BUG at slab.c:815) maybe devfs
Date: Thu, 20 Dec 2001 16:15:10 -0800 [thread overview]
Message-ID: <3C227F0E.E6A9CF76@zip.com.au> (raw)
In-Reply-To: <3C210AB9.5000900@suhr.home.cs.tu-berlin.de>, <3C210AB9.5000900@suhr.home.cs.tu-berlin.de> <200112202338.fBKNcCI05673@vindaloo.ras.ucalgary.ca>
Richard Gooch wrote:
>
> Gregor Suhr writes:
> > ...
> > kernel BUG at slab.c:815!
Somebody tried to create the same cache twice. This can
happen when loading a buggy module the second time, various
things.
Please, apply this patch and run it again.
--- linux-2.4.17-rc2/mm/slab.c Tue Dec 18 19:37:31 2001
+++ linux-akpm/mm/slab.c Thu Dec 20 16:14:19 2001
@@ -811,8 +811,10 @@ next:
kmem_cache_t *pc = list_entry(p, kmem_cache_t, next);
/* The name field is constant - no lock needed. */
- if (!strcmp(pc->name, name))
+ if (!strcmp(pc->name, name)) {
+ printk(__FUNCTION__ ": %s\n", name);
BUG();
+ }
}
}
next prev parent reply other threads:[~2001-12-21 0:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 21:46 OOPS at boot in 2.4.17-rc[12] (kernel BUG at slab.c:815) maybe devfs Gregor Suhr
2001-12-20 23:38 ` Richard Gooch
2001-12-21 0:15 ` Andrew Morton [this message]
[not found] ` <3C23842A.20407@Suhr.home.cs.tu-berlin.de>
[not found] ` <200112211926.fBLJQ7814544@vindaloo.ras.ucalgary.ca>
[not found] ` <3C2392EC.6050306@Suhr.home.cs.tu-berlin.de>
2001-12-21 20:05 ` Richard Gooch
[not found] ` <3C23A022.5040307@Suhr.home.cs.tu-berlin.de>
2001-12-21 22:02 ` Richard Gooch
[not found] ` <3C23843A.3040904@Suhr.home.cs.tu-berlin.de>
2001-12-21 19:16 ` Richard Gooch
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=3C227F0E.E6A9CF76@zip.com.au \
--to=akpm@zip.com.au \
--cc=gregor@suhr.home.cs.tu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.