Oops in sunrpc:rpc_shutdown_client
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Debian) |
Fix Released
|
Unknown
|
|||
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Hardy |
Fix Released
|
High
|
Manoj Iyer |
Bug Description
SRU justification:
Impact: Oops in sunrpc:
Fix: likely related to: #212485 kernel bug rpc nfs client. Backported patch to Hardy.
Test: Test kernel in http://
---
Having setup an nfsv4 export in /etc/exports:
/store /192.168.
I restarted the nfs-kernel-server service:
# /etc/init.
# /etc/init.
After ~15s, we see the callback being attempted twice and an oops:
[ 2361.807753] nfs4_cb: server 194.202.174.13 not responding, timed out
[ 2361.808059] nfs4_cb: server 194.202.174.13 not responding, timed out
[ 2361.808085] Unable to handle kernel NULL pointer dereference at 0000000000000018 RIP:
[ 2361.808098] [<ffffffff8830d
[ 2361.808140] PGD 7dfb7067 PUD 7dfae067 PMD 0
[ 2361.808155] Oops: 0000 [1] SMP
[ 2361.808166] CPU 1
[ 2361.808174] Modules linked in: nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs ipv6 ac sbs sbshc battery dock video output iptable_filter ip_tables x_tables xfs parport_pc lp parport af_packet loop container serio_raw cfi_cmdset_0002 cfi_util jedec_probe button cfi_probe gen_probe ck804xrom mtd chipreg shpchp pci_hotplug k8temp i2c_nforce2 map_funcs psmouse i2c_core evdev pcspkr ext3 jbd mbcache sg sd_mod pata_acpi sata_nv tg3 ata_generic pata_amd libata scsi_mod ehci_hcd ohci_hcd usbcore thermal processor fan fbcon tileblit font bitblit softcursor fuse
[ 2361.808369] Pid: 5877, comm: nfs4_cb_probe Not tainted 2.6.24-19-generic #1
[ 2361.808380] RIP: 0010:[<
[ 2361.808404] RSP: 0018:ffff81007d
[ 2361.808412] RAX: 00000000fffffffb RBX: ffff81007b9dac00 RCX: ffff810001019480
[ 2361.808424] RDX: 0000000000000003 RSI: 0000000000000000 RDI: 0000000000000000
[ 2361.808435] RBP: 0000000000000018 R08: ffffffff8833a490 R09: ffff81007b9c2000
[ 2361.808446] R10: 0000000000000000 R11: ffffffff80287840 R12: 0000000000000000
[ 2361.808471] R13: 0000000000000000 R14: ffff81007dff3eb8 R15: 0000000000000000
[ 2361.808496] FS: 00007fcf7f91a6e
[ 2361.808533] CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
[ 2361.808556] CR2: 0000000000000018 CR3: 000000007dfb6000 CR4: 00000000000006e0
[ 2361.808580] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 2361.808605] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 2361.808630] Process nfs4_cb_probe (pid: 5877, threadinfo ffff81007dff2000, task ffff81007df68fc0)
[ 2361.808668] Stack: 0000000000000000 0000000000000000 0000000000000282 0000000000000282
[ 2361.808713] ffff81007d5bd180 ffffffff88313459 ffff81007b9dac00 ffff81007b9dac00
[ 2361.808755] ffffffff883888f0 0000000000000000 0000000000000000 ffffffff8838895c
[ 2361.808784] Call Trace:
[ 2361.808829] [<ffffffff88313
[ 2361.808871] [<ffffffff88388
[ 2361.808901] [<ffffffff88388
[ 2361.808931] [<ffffffff80253
[ 2361.808957] [<ffffffff8020d
[ 2361.808984] [<ffffffff80253
[ 2361.809006] [<ffffffff8020d
[ 2361.809028]
[ 2361.809044]
[ 2361.809044] Code: 49 39 6c 24 18 0f 84 84 00 00 00 4c 89 e7 e8 88 67 00 00 49
[ 2361.809132] RIP [<ffffffff8830d
[ 2361.809165] RSP <ffff81007dff3ea0>
[ 2361.809185] CR2: 0000000000000018
[ 2361.809493] ---[ end trace 949da475918d45ed ]---
likely related to: #212485 kernel bug rpc nfs client.
Fixed apparently [http://
commit 63c86716ea34ad9
commit 46f8a64bae11f5c
http://
http://
Changed in linux: | |
status: | Unknown → New |
Changed in linux (Ubuntu Hardy): | |
assignee: | nobody → Manoj Iyer (manjo) |
importance: | Undecided → High |
milestone: | none → ubuntu-8.04.3 |
status: | New → In Progress |
Changed in linux (Ubuntu Hardy): | |
status: | Incomplete → In Progress |
Changed in linux (Ubuntu Hardy): | |
status: | In Progress → Fix Committed |
description: | updated |
tags: |
added: verification-done removed: verification-needed |
Changed in linux (Debian): | |
status: | New → Fix Released |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e . I have classified this bug as a bug in linux. /wiki.ubuntu. com/ReportingBu gs.
For future reference you might be interested to know that a lot of applications have bug reporting functionality built in to them. This can be accessed via the Report a Problem option in the Help menu for the application with which you are having an issue. You can learn more about this feature at https:/