Messages in this thread | | | Date | Tue, 17 Oct 2000 22:06:19 +0200 | From | Roger Larsson <> | Subject | Re: [BUG]: Ext2 Corruption in test10pre3 (incl. Oops) |
| |
Linus Torvalds wrote: > > 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. > > Linus > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > Please read the FAQ at http://www.tux.org/lkml/
Hmm.. Might this problem be related to...
Tigrans: > Subject: test10-pre1 BUG at page_alloc.c:221!
Quintelas: > Subject: I've got the BAD_RANGE BUG in rmqueue!!! (Pre9-4)
Richard Guenther > Subject: [OOPS][BUG] with 2.4.0-test9 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
| |