All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Oleg Drokin <green@namesys.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: reiserfs oops [2.5.65]
Date: Thu, 20 Mar 2003 13:24:09 +0000	[thread overview]
Message-ID: <20030320132409.GA19042@suse.de> (raw)
In-Reply-To: <20030320112559.A12732@namesys.com>

On Thu, Mar 20, 2003 at 11:25:59AM +0300, Oleg Drokin 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.

There's lots of "slab error in cache_alloc_debugcheck_after()"
warnings. cache reiser_inode_cache memory after object was overwritten

Some call traces.
 check_poison_obj <- kmem_cache_alloc <- reierfs_alloc_inode <-
 reiserfs_alloc_inode <- alloc_inode <- get_new_inode <-
 reiserfs_init_locked <- reiserfs_find_actor <- reiserfs_iget <-
 reiserfs_find_actor <- reiserfs_init_locked_inode <- reiserfs_lookup <-
 real_lookup <- do_lookup <- link_path_walk <- kmem_cache_alloc <-
 __user_walk <- vfs_lstat <- sys_lstat64 <- syscall_call

Slab corruption: start=c70c7044, expend=c70c7213 problemat=c70c7044
Last user: [<c0280dcb>](reiserfs_alloc_inode+0x1b/0x30)
Data: (lots of hex)

I'll give that box a run of memtest to rule out memory corruption
problems. I'll also hook up a serial terminal tonight to catch tomorrow
nights 'activity' in full 8-)

		Dave


  parent reply	other threads:[~2003-03-20 13:13 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 [this message]
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     ` reiserfs oops [2.5.65] Oleg Drokin
2003-03-21 11:54       ` 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=20030320132409.GA19042@suse.de \
    --to=davej@codemonkey.org.uk \
    --cc=green@namesys.com \
    --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.