NFS: Unable to handle kernel NULL pointer dereference at nfs_set_page_dirty+0xd/0x5d in 2.6.21rc7-git6

From: Andi Kleen
Date: Tue Apr 24 2007 - 10:06:11 EST

Another issue hit during LTP testing over nfsroot; this time
on a larger box (4 cores; 6GB RAM; x86-64)

NFS doesn't seem to be in a good shape for .21


Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP:
[<ffffffff8031076b>] nfs_set_page_dirty+0xd/0x5d
PGD 115735067 PUD 11a60a067 PMD 0
Oops: 0000 [1] SMP
Modules linked in:
Pid: 8476, comm: doio Not tainted 2.6.21-rc7-git6 #20
RIP: 0010:[<ffffffff8031076b>] [<ffffffff8031076b>] nfs_set_page_dirty+0xd/0x5d
RSP: 0000:ffff8101157b7d98 EFLAGS: 00010292
RAX: 0000000000000000 RBX: ffff81011f9462d8 RCX: 0000000000000004
RDX: ffff810117840430 RSI: 0000000000000004 RDI: ffff81011f9462d8
RBP: ffff81011f9462d8 R08: ffff81011c03f205 R09: ffff81011c03f202
R10: ffff81011a41f228 R11: ffffffff8031075e R12: 0000000114a6cc40
R13: ffff810117840430 R14: ffff81011b3bdb88 R15: ffff81011fd847b0
FS: 00002af288f0bb00(0000) GS:ffff81011c03f0c0(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000000 CR3: 0000000117297000 CR4: 00000000000006e0
Process doio (pid: 8476, threadinfo ffff8101157b6000, task ffff81011b8c8240)
Stack: ffff81011f9462d8 ffff81011f9462d8 ffff81011f9462d8 ffffffff8025a0bc
ffff810114a6cc40 ffffffff80260b75 ffff81011fd77f78 000000011fef0340
00002af289388714 ffff81011a4f04c0 0000000000000c40 ffff81011a952248
Call Trace:
[<ffffffff8025a0bc>] set_page_dirty_balance+0x9/0x39
[<ffffffff80260b75>] __handle_mm_fault+0x43e/0x9e1
[<ffffffff80544f7e>] do_page_fault+0x42b/0x7ad
[<ffffffff80265815>] do_mmap_pgoff+0x619/0x785
[<ffffffff8027b951>] sys_newfstat+0x20/0x29
[<ffffffff805433ad>] error_exit+0x0/0x84

Code: 48 8b 28 48 8d 7d a8 e8 eb 26 23 00 48 89 df e8 e9 e6 ff ff
RIP [<ffffffff8031076b>] nfs_set_page_dirty+0xd/0x5d
RSP <ffff8101157b7d98>
CR2: 0000000000000000
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at