[lkml]   [2003]   [Mar]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: reiserfs oops [2.5.65]
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-)


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:34    [W:0.086 / U:1.756 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site