lkml.org 
[lkml]   [2000]   [Aug]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.4.0-test6-pre2 EXT2-related Lockup [Was: Re: 2.4.0-test6-pre2 man euid error]


On Fri, 4 Aug 2000, clubneon wrote:

> It was probally the Call Trace. My most recent oops looked just like
> that. Very, very, very long call trace. Since my oopses don't seem to be
> making it to disk, I've been copying them by hand. This one scrolled off
> the screen, so there wasn't much I could do.

Urgh. That assumes either
a) recursion in ext2_get_block() or
b) ext2_get_block() called from interrupt context.
The latter is obviously deadly, but I don't see such callers appearing
lately.

The former... WTF? I might believe it if the trace would go through
buffer.c, but it seems to stay in ext2/inode.c...

It almost looks like gcc turned loop into tail recursion, but it shouldn't
be doing it, should it? Just in case, could you send me fs/ext2/inode.o
and version of your gcc?

Aside of these 3 variants I see no other possible cause for such trace.
Linus, do you see any other possible reason for trace of that kind?


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

\
 
 \ /
  Last update: 2005-03-22 13:58    [from the cache]
©2003-2011 Jasper Spaans