lkml.org 
[lkml]   [2004]   [Aug]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Possible dcache BUG


On Fri, 6 Aug 2004, Chris Shoemaker wrote:
>
> I _was_ able to find the attached oops, but I don't think I have the
> corresponding object files, so I hope the decoding it contains is
> good enough.

It's fine.

It oopses on

inode->i_sb->s_op

where "i_sb" is bad and contains the pointer "0x0b7eebf8" which is
definitely not a valid kernel pointer.

There's a few other strange details in your oops report too. One being
that the inode pointer (in %ebx, apparently) doesn't show on the stack
where I'd expect it to show. Hmm. That might be just a different compiler
issue, though.

Anyway, this does look somewhat like the ones Gene is seeing. If I had to
guess, I'd guess that either the inode pointer is bad, or it's just stale
from an inode that has already been free'd. Most likely because of
prune_dcache() having had a corrupt LRU list with a stale/corrupt entry.

That would blow the prefetch theory out of the water.

Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2009-11-18 23:46    [W:0.165 / U:0.032 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site