Alexander Viro wrote:
>
> On Fri, 2 Mar 2001, TimO wrote:
>
> > eax: 00000000 ebx: 00000000 ecx: 00000000 edx: 00000000
> [snip]
> > >>EIP; c0142a52 <get_new_inode+b2/160> <=====
> > Trace; c0142ca6 <iget4+b6/d0>
> > Trace; c0145f01 <proc_get_inode+41/120>
> > Trace; c014601a <proc_read_super+3a/b0>
> > Trace; c01349a4 <read_super+104/180>
> > Trace; c0134f7a <kern_mount+2a/80>
> > Trace; c0107007 <init+7/110>
> > Trace; c01074b8 <kernel_thread+28/40>
> > Code; c0142a52 <get_new_inode+b2/160>
> > 00000000 <_EIP>:
> > Code; c0142a52 <get_new_inode+b2/160> <=====
> [snip]
>
> Lovely. sb->s_op == NULL in iget(). The thing being, proc_read_super()
> explicitly sets ->s_op to non-NULL. Oh, and that area hadn't changed since
> 2.4.2, so I'd rather suspect the b0rken build. Can you reproduce it?
>
> Cheers,
> Al
Not anymore; rm -rf seems to have fixed it (make mrproper didn't).
Guess
I should have tried that before posting. Don't know how it got screwed
up; only 2 patches applied to this tree.
Thanks,
===============
-- Tim
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
