[lkml]   [2000]   [Oct]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [BUG]: Ext2 Corruption in test10pre3 (incl. Oops)

On Tue, 17 Oct 2000, Alexander Viro wrote:
> > Trace; c014efde <read_inode_bitmap+3e/90>
> > Trace; c014f240 <load_inode_bitmap+210/230>
> > Trace; c014f6af <ext2_new_inode+29f/700>
> > Trace; c021e87e <unix_write_space+2e/50>
> Huh?
> > Trace; c01523af <ext2_create+1f/c0>
> The rest of trace is OK, but WTF is net/unix/*.c code is doing here?

The traces always (or almost always) have crud in them - it's not a real
stack-trace, it's just a printout of the stack contents that match
addresses in the text region. So the unix_write_space thing was probably
from the previous system call and just hadn't been overwritten.


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

 \ /
  Last update: 2005-03-22 12:41    [W:0.080 / U:12.480 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site