From: Grzegorz Jaskiewicz <gj@pointblue.com.pl>
To: lkml <linux-kernel@vger.kernel.org>
Cc: jaharkes@cs.cmu.edu, codalist@TELEMANN.coda.cs.cmu.edu
Subject: OUPS 2.5.69-bk19 coda-inode.c/slab.c
Date: 26 May 2003 18:45:40 +0100 [thread overview]
Message-ID: <1053971135.1968.6.camel@nalesnik.localhost> (raw)
following BUG() is started when coda is included into kernel. I have not
tried module, but i bet it will couse the same error.
coda_init_inodecache runs kmem_cache_create which couses oups.
Removing following lines from slab.c renders system stable.
But this is not a cure. As i am not using coda it self, i really don't
know if it is running stable.
slab.c snip:
/*
* Always checks flags, a caller might be expecting debug
* support which isn't available.
*/
/*
if (flags & ~CREATE_MASK){
printk("dupa2\n");
_BUG();
BUG();
}
this is in kmem_cache_create fn.
--
Grzegorz Jaskiewicz <gj@pointblue.com.pl>
K4 labs
next reply other threads:[~2003-05-26 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-26 17:45 Grzegorz Jaskiewicz [this message]
2003-05-27 0:43 ` OUPS 2.5.69-bk19 coda-inode.c/slab.c Jan Harkes
2003-05-27 9:23 ` Grzegorz Jaskiewicz
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=1053971135.1968.6.camel@nalesnik.localhost \
--to=gj@pointblue.com.pl \
--cc=codalist@TELEMANN.coda.cs.cmu.edu \
--cc=jaharkes@cs.cmu.edu \
--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