From: Oleg Drokin <green@namesys.com>
To: Dave Jones <davej@codemonkey.org.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: reiserfs oops [2.5.65]
Date: Fri, 21 Mar 2003 12:14:55 +0300 [thread overview]
Message-ID: <20030321121454.A17440@namesys.com> (raw)
In-Reply-To: <20030320132409.GA19042@suse.de>
Hello!
On Thu, Mar 20, 2003 at 01:24:09PM +0000, Dave Jones wrote:
> > Hm, very interesting. Thank you.
> > I've seen this once too, but on kernel patched with lots of unrelated and
> > possibly memory corrupting stuff.
> > I will look at it more closely.
> > BTW, it oopsed not in find. Is your box SMP?
> Same box committed seppuku overnight, this time in a different way.
Hm, am I missing something?
So it died in the morning yesterday, but before that it died again? Or were those
two different nights? ;)
> There's lots of "slab error in cache_alloc_debugcheck_after()"
> warnings. cache reiser_inode_cache memory after object was overwritten
This second oops and first BUG you quoted indicate that internal slab structures
(I think second oops happened in the middle of list_del) were corrupted, not
the guarded data itself.
At least I think so.
Can I take a look at your .config?
Thank you.
Bye,
Oleg
next prev parent reply other threads:[~2003-03-21 9:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 14:10 reiserfs oops [2.5.65] Dave Jones
2003-03-20 8:25 ` Oleg Drokin
2003-03-20 11:48 ` Dave Jones
2003-03-20 13:24 ` Dave Jones
2003-03-20 14:03 ` Dave Jones
2003-03-21 0:59 ` Andrew Morton
2003-03-20 23:13 ` Dave Jones
2003-03-20 23:34 ` Randy.Dunlap
2003-03-22 19:36 ` Nicholas Wourms
2003-03-25 16:15 ` Bill Davidsen
2003-03-31 18:53 ` [announce] kmsgdump for 2.5.65/66 Randy.Dunlap
2003-03-31 19:17 ` Nicholas Wourms
2003-03-31 20:44 ` Randy.Dunlap
2003-03-21 9:14 ` Oleg Drokin [this message]
2003-03-21 11:54 ` reiserfs oops [2.5.65] Dave Jones
2003-03-21 13:42 ` Oleg Drokin
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=20030321121454.A17440@namesys.com \
--to=green@namesys.com \
--cc=davej@codemonkey.org.uk \
--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 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.