Ubuntu
linux-source-2.6.17 package

linux-image-2.6.17-50-generic crash when mounting NFS4

Bug #83205 reported by Daniel J Blueman
4
Affects Status Importance Assigned to Milestone
linux-source-2.6.17 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.17-50-generic

I experience the kernel oopsing in the context of the 'mount' process when I:

(maybe related)
# echo 43407 >/proc/sys/fs/nfs/nfs_callback_tcpport

# mount x1.home:/ /store -t nfs4

This works perfectly on 2.6.19. Version is Edgy with current updates and proposed 2.6.27-50 kernel - i686 arch.

The kernel logs contain:

[17179753.760000] BUG: unable to handle kernel paging request at virtual address 5f637072
[17179753.760000] printing eip:
[17179753.760000] c0186d03
[17179753.760000] *pde = 00000000
[17179753.760000] Oops: 0000 [#1]
[17179753.760000] SMP
[17179753.760000] Modules linked in: xt_state ip_conntrack nfnetlink xt_tcpudp iptable_filter ip_tables x_tables ip
v6 nfs lockd sunrpc sonypi speedstep_centrino cpufreq_userspace cpufreq_stats freq_table cpufreq_powersave cpufreq_
ondemand cpufreq_conservative video tc1100_wmi sbs sony_acpi pcc_acpi i2c_ec i2c_core hotkey dock dev_acpi button b
attery container ac asus_acpi af_packet sbp2 parport_pc lp parport sk98lin pcmcia snd_hda_intel snd_hda_codec snd_p
cm_oss snd_mixer_oss joydev sky2 snd_pcm tsdev tifm_7xx1 snd_timer tifm_core yenta_socket rsrc_nonstatic pcmcia_cor
e sg snd shpchp psmouse pci_hotplug serio_raw intel_agp agpgart soundcore snd_page_alloc evdev ext3 jbd ehci_hcd oh
ci1394 ieee1394 uhci_hcd usbcore ide_generic sd_mod ata_piix libata scsi_mod ide_cd cdrom piix generic thermal proc
essor fan fbcon tileblit font bitblit softcursor vesafb capability commoncap
[17179753.760000] CPU: 0
[17179753.760000] EIP: 0060:[<c0186d03>] Not tainted VLI
[17179753.760000] EFLAGS: 00010206 (2.6.17-50-generic #2)
[17179753.760000] EIP is at alloc_vfsmnt+0x93/0xf0
[17179753.760000] eax: 00000000 ebx: f7eb3940 ecx: ffffffff edx: 00000000
[17179753.760000] esi: f8cdfb0c edi: 5f637072 ebp: 5f637072 esp: f5819d28
[17179753.760000] ds: 007b es: 007b ss: 0068
[17179753.760000] Process mount (pid: 4780, threadinfo=f5818000 task=dfec3a90)
[17179753.760000] Stack: dfffd4e4 000000d0 f8ccf335 f8cdfb0c f8ccf335 f8ce36a0 c0171814 00000000
[17179753.760000] 5f637072 00000000 f57f353c f8ccf335 f8cdfb0c 00000000 f8ce36a0 c018dc7b
[17179753.760000] 00000000 f8d64a14 dfce9c00 00000008 f8d52207 f8ccad94 f8cbbbff c18cc800
[17179753.760000] Call Trace:
[17179753.760000] <c0171814> vfs_kern_mount+0x24/0x150 <c018dc7b> simple_pin_fs+0x8b/0xb0
[17179753.760000] <f8ccad94> rpc_get_mount+0x14/0x20 [sunrpc] <f8cbbbff> rpc_new_client+0x17f/0x330 [sunrpc]
[17179753.760000] <c02234d0> get_random_bytes+0x20/0x30 <f8cbcba9> rpc_create_client+0x19/0x50 [sunrpc]
[17179753.760000] <f8d329fc> nfs4_get_sb+0x61c/0x6f0 [nfs] <c01718a0> vfs_kern_mount+0xb0/0x150
[17179753.760000] <c0171999> do_kern_mount+0x39/0x60 <c01882d0> do_mount+0x450/0x760
[17179753.760000] <c015921a> __handle_mm_fault+0x4ea/0x900 <c026921c> sk_reset_timer+0xc/0x20
[17179753.760000] <c02a6628> __tcp_push_pending_frames+0x218/0x8a0 <c01513a6> __alloc_pages+0x56/0x330
[17179753.760000] <c0187000> copy_mount_options+0x40/0x150 <c0188657> sys_mount+0x77/0xc0
[17179753.760000] <c0102fbb> sysenter_past_esp+0x54/0x79
[17179753.760000] Code: 89 43 40 8d 43 48 89 40 04 89 43 48 8d 43 50 89 40 04 89 43 50 8d 43 58 89 1b 89 43 58 89 4 0 04 74 43 b9 ff ff ff ff 89 ef 89 d0 <f2> ae f7 d1 49 83 c1 01 b2 d0 89 c8 89 4c 24 04 e8 c8 03 fe ff
[17179753.760000] EIP: [<c0186d03>] alloc_vfsmnt+0x93/0xf0 SS:ESP 0068:f5819d28

Tags: kernel-oops
Revision history for this message
Daniel J Blueman (danielblueman) wrote :

Confirmed setting the NFS 4 callback port doesn't affect this bug.

Reproducer is to just mount an NFS4 directory.

Revision history for this message
Daniel J Blueman (danielblueman) wrote :

Confirmed the step of setting the NFS 4 callback port isn't needed to reproduce this bug.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are currently reviewing bug reports regarding older kernel versions. After review we feel this bug does not meet the criteria for a stable release update and are setting this bug's status to "Won't Fix". For more information regarding stable release updates, please refer to https://wiki.ubuntu.com/StableReleaseUpdates .

However, now that the 7.10, codename Gutsy Gibbon, release of Ubuntu is out, we were wondering if you can still reproduce this issue. Could you please download and try the new version of Ubuntu from http://www.ubuntu.com/getubuntu/download and report back your results? If the issue is still present in the new release, please attach the output from the following commands:

* uname -a > uname-a.log
* cat /proc/version_signature > version.log
* after a fresh boot execute - dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

Please be sure to attach each file as a separate attachment. For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . I have subscribed to the bug report and if you do recreate the bug please set the bug's status to Incomplete so we can proceed with the triaging process. Thanks again and we appreciate your help and feedback.

Changed in linux-source-2.6.17:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.