On Mar 27, 2003 18:07, Oleg Drokin wrote:
> On Thu, Mar 27, 2003 at 01:22:07AM -0800, Bill Huey wrote:
> > NFS problems with reiserfs:
>
> Can you reproduce it with 2.5.66?
Well, I can. I got following Oops with 2.5.66-bk3:
<1>Unable to handle kernel NULL pointer dereference at virtual address
00000000
printing eip:
00000000
*pde = 00000000
Oops: 0000 [#4]
CPU: 0
EIP: 0060:[<00000000>] Tainted: GF
EFLAGS: 00010206
EIP is at 0x0
eax: 00000000 ebx: cd6ba014 ecx: c038a008 edx: 00000006
esi: c1382400 edi: 11270000 ebp: cd6e3ea4 esp: cd6e3e6c
ds: 007b es: 007b ss: 0068
Process nfsd (pid: 624, threadinfo=cd6e2000 task=cd780cc0)
Stack: c01de985 c1382400 cd6e3e98 cd6e3e8c d4a535f0 cb05e6d4 cd6ba014 cd6ba004
00000004 00000002 00000002 0014bfca 00000004 00000004 cd6e3eec d4a53a3e
c1382400 cd6ba014 00000006 00000006 d4a535f0 cb05e6d4 cd6ba004 cd6ba8e8
Call Trace:
[<c01de985>] reiserfs_decode_fh+0xbd/0xc4
[<d4a535f0>] gcc2_compiled.+0x0/0x100 [nfsd]
[<d4a53a3e>] fh_verify+0x34e/0x4f8 [nfsd]
[<d4a535f0>] gcc2_compiled.+0x0/0x100 [nfsd]
[<d4a27f80>] ip_table+0x0/0x400 [sunrpc]
[<d4a54c4f>] nfsd_access+0x27/0xf0 [nfsd]
[<d4a5b716>] nfsd3_proc_access+0xb6/0xc4 [nfsd]
[<d4a6ff70>] nfsd_procedures3+0x90/0x318 [nfsd]
[<d4a51ae8>] nfsd_dispatch+0xd0/0x188 [nfsd]
[<d4a0b50d>] svc_process+0x3cd/0x660 [sunrpc]
[<d4a6ff70>] nfsd_procedures3+0x90/0x318 [nfsd]
[<d4a701f8>] nfsd_version3+0x0/0x28 [nfsd]
[<d4a516dd>] nfsd+0x411/0x74c [nfsd]
[<d4a512cc>] nfsd+0x0/0x74c [nfsd]
[<d4a512cc>] nfsd+0x0/0x74c [nfsd]
[<d4a6f578>] nfsd_list+0x0/0x8 [nfsd]
[<c01081e5>] kernel_thread_helper+0x5/0xc
Code: Bad EIP value.
> sb->s_export_op->find_exported_dentry is NULL
> in reiserfs_decode_fh, well. In fact we never set this field at all.
> What is supposed to be there, anyway?
> I guess following patch should fix the problem.
For me it looks good, so I'll give it a try...
> In fact I guess somebody should put find_exported_dentry() declaration to
> include/linux/fs.h or something like that.
> Also absolutely the same problem must exist if you try to export fat
filesystem.
I didn't try that...
Regards
Thomas
-
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/
This archive was generated by hypermail 2b29 : Mon Mar 31 2003 - 22:00:31 EST