xfs
[Top] [All Lists]

Unable to handle kernel NULL pointer dereference with 2.4.19-rc3-xfs

To: linux-xfs@xxxxxxxxxxx
Subject: Unable to handle kernel NULL pointer dereference with 2.4.19-rc3-xfs
From: James Pearson <james-p@xxxxxxxxxxxxxxxxxx>
Date: Tue, 30 Jul 2002 12:07:55 +0100
Organization: Moving Picture Company
Sender: owner-linux-xfs@xxxxxxxxxxx
I've just had the following oops with nfsd on an XFS file system using a
CVS kernel from July 22nd - not sure if it's XFS or NFS related ...

I'm running this kernel as I previous had problems with 2.4.18-xfs-1.1
and nfsd locking up -  see:

http://marc.theaimsgroup.com/?l=linux-xfs&m=102579948531207&w=2

This time I get similar symptoms, but I guess it may not be related as I
get an oops.

Thanks

James Pearson


Unable to handle kernel NULL pointer dereference at virtual address
00000090
c01d4a88
*pde = 00000000
Oops: 0002
CPU:    0
EIP:    0010:[<c01d4a88>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010202
eax: 00000070   ebx: 00000070   ecx: c02d2a8c   edx: 00000090
esi: 00000008   edi: 00000008   ebp: f2974d24   esp: f71f9e14
ds: 0018   es: 0018   ss: 0018
Process nfsd (pid: 1241, stackpage=f71f9000)
Stack: ffffffe8 c01a81f6 00000070 00000000 00000000 00000000 f7917c00
f71f9e80 
       0000000a f7248800 c01c042b f7917c00 00000000 7097d0a1 00000000
00000008 
       f71f9e60 00000000 00000000 e59c2400 f7917c00 f7320814 f779c400
c01d2d92 
Call Trace:    [<c01a81f6>] [<c01c042b>] [<c01d2d92>] [<f89d7ed8>]
[<f89d831f>]
  [<f89d8841>] [<f89deff7>] [<f89e5fa0>] [<f89d65a7>] [<f89e5fa0>]
[<f8995da3>]
  [<f89e5958>] [<f89e5978>] [<f89d63ab>] [<c0107296>] [<f89d61a0>]
Code: f0 fe 4b 20 0f 88 dc 02 00 00 66 83 7b 06 00 74 3f 0f b7 43 

>>EIP; c01d4a88 <mraccessf+8/70>   <=====
Trace; c01a81f6 <xfs_iget+116/170>
Trace; c01c042b <xfs_vget+4b/d8>
Trace; c01d2d92 <linvfs_fh_to_dentry+72/fc>
Trace; f89d7ed8 <[nfsd]nfsd_get_dentry+28/b0>
Trace; f89d831f <[nfsd]find_fh_dentry+3f/340>
Trace; f89d8841 <[nfsd]fh_verify+221/420>
Trace; f89deff7 <[nfsd]nfsd3_proc_getattr+97/b0>
Trace; f89e5fa0 <[nfsd]nfsd_procedures3+20/2c0>
Trace; f89d65a7 <[nfsd]nfsd_dispatch+b7/17b>
Trace; f89e5fa0 <[nfsd]nfsd_procedures3+20/2c0>
Trace; f8995da3 <[sunrpc]svc_process+333/4e8>
Trace; f89e5958 <[nfsd]nfsd_version3+0/10>
Trace; f89e5978 <[nfsd]nfsd_program+0/18>
Trace; f89d63ab <[nfsd]nfsd+20b/350>
Trace; c0107296 <kernel_thread+26/30>
Trace; f89d61a0 <[nfsd]nfsd+0/350>
Code;  c01d4a88 <mraccessf+8/70>
00000000 <_EIP>:
Code;  c01d4a88 <mraccessf+8/70>   <=====
   0:   f0 fe 4b 20               lock decb 0x20(%ebx)   <=====
Code;  c01d4a8c <mraccessf+c/70>
   4:   0f 88 dc 02 00 00         js     2e6 <_EIP+0x2e6> c01d4d6e
<.text.lock.mrlock+24/96>
Code;  c01d4a92 <mraccessf+12/70>
   a:   66 83 7b 06 00            cmpw   $0x0,0x6(%ebx)
Code;  c01d4a97 <mraccessf+17/70>
   f:   74 3f                     je     50 <_EIP+0x50> c01d4ad8
<mraccessf+58/70>
Code;  c01d4a99 <mraccessf+19/70>
  11:   0f b7 43 00               movzwl 0x0(%ebx),%eax


26 warnings and 3 errors issued.  Results may not be reliable.


<Prev in Thread] Current Thread [Next in Thread>