Bug 121926
Summary: | oops on smbfs | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Srihari Vijayaraghavan <noldoli> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | bugzilla, henryl, richard_theil |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-08-09 11:46:17 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Srihari Vijayaraghavan
2004-04-29 05:28:22 UTC
And oh, the remote machine, whose smb share I am trying to mount, is a Windows NT 4 Work Station (SP6a). I am not sure if that matters. Confirmed on FC2 Release as well. For me the remote system share is smaba on FC1 with all current errata. As the trace indecates Nautilus is involved some how. There are no problems mounting/browsing the same share from runlevel 3. (Nautilus not running) I'll attach a copy of my oops as well: kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000 kernel: printing eip: kernel: 00000000 kernel: *pde = 00000000 kernel: Oops: 0000 [#1] kernel: CPU: 0 kernel: EIP: 0060:[<00000000>] Not tainted kernel: EFLAGS: 00210246 (2.6.5-1.358) kernel: EIP is at 0x0 kernel: eax: 0c13d080 ebx: 1558d290 ecx: 0214edcd edx: 12de4fa0 kernel: esi: 04079024 edi: 03040f20 ebp: 0c13d080 esp: 12de4f14 kernel: ds: 007b es: 007b ss: 0068 kernel: Process nautilus (pid: 2201, threadinfo=12de4000 task=153ef330) kernel: Stack: 26e6b976 12de4f38 00000000 04079000 08b01b54 0a427e18 1e2c6080 0214edcd mount.smbfs[5690]: [2004/05/19 09:22:59, 0] client/smbmount.c:send_fs_socket(406) kernel: 12de4fa0 00000000 0215fe39 0c13d080 00000000 00000000 04079000 00000002 mount.smbfs[5690]: mount.smbfs: entering daemon mode for service \\share\public, pid=5690 kernel: 00000000 00000000 00000001 00000004 00200246 26e73020 0a427e80 0c13d080 kernel: Call Trace: kernel: [<26e6b976>] smb_readdir+0x346/0x3f1 [smbfs] kernel: [<0214edcd>] filldir64+0x0/0x12e kernel: [<0215fe39>] elf_core_dump+0x8a8/0x94b kernel: [<0214eaba>] vfs_readdir+0x7a/0x9b kernel: [<0214edcd>] filldir64+0x0/0x12e kernel: [<0214ef60>] sys_getdents64+0x65/0xaa kernel: [<0214e26c>] generic_file_fcntl+0xd7/0x140 kernel: kernel: Code: Bad EIP value. The good news is that in vanilla 2.6.7-rc2 it works great (no oops, and data is visible). I will see if I can work out the diff between Fedora 2's kernel (2.6.5-1.358) and 2.5.7-rc2, which fixes this fault. Thanks Hari PS: I am on FC2 final like Scott Russell. There is no diff between FC2 and 2.6.7-rc2 smbfs files. I am lost (Maybe something was fixed at the VFS level, I do not know). If you want me to test some patches etc., please let me know. Thanks Hari We're working on an update based on 2.6.7-rc2 for FC2, you can get a preliminary version of that kernel from http://people.redhat.com/arjanv/2.6/ Thanks Arjan. I have used the kernel-2.6.6-1.406.i686.rpm package from that URL, but unfortunately that does not fix the problem. Here is the oops report from that kernel: smb_lookup: find //.Trash-"deleted-user-name" failed, error=-5 Unable to handle kernel NULL pointer dereference at virtual address 00000000 printing eip: 00000000 *pde = 00000000 Oops: 0000 [#1] Modules linked in: smbfs snd_mixer_oss snd_intel8x0 snd_ac97_codec snd_pcm snd_timer snd_page_alloc gameport snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore parport_pc lp parport autofs4 sunrpc e100 mii ipt_REJECT ipt_state ip_conntrack iptable_filter ip_tables floppy sg scsi_mod microcode dm_mod uhci_hcd ehci_hcd button battery asus_acpi ac i830 ipv6 ext3 jbd CPU: 0 EIP: 0060:[<00000000>] Not tainted EFLAGS: 00210246 (2.6.6-1.406) EIP is at 0x0 eax: 0f479280 ebx: 12b966d8 ecx: 0214da2d edx: 11161fa0 esi: 0f3f0024 edi: 031a7e00 ebp: 0f479280 esp: 11161f14 ds: 007b es: 007b ss: 0068 Process nautilus (pid: 2807, threadinfo=11161000 task=11107730) Stack: 2253b982 11161f38 00000000 0f3f0000 21749638 0f3f4e18 0f5af50c 0214da2d 11161fa0 00000000 fffdf71c 0f479280 00000000 00000000 0f3f0000 00000002 00000000 00000000 00000001 00000004 00200246 22543060 0f3f4e80 0f479280 Call Trace: [<2253b982>] smb_readdir+0x346/0x3f1 [smbfs] [<0214da2d>] filldir64+0x0/0x12e [<0214d71a>] vfs_readdir+0x7a/0x9b [<0214da2d>] filldir64+0x0/0x12e [<0214dbc0>] sys_getdents64+0x65/0xaa [<0214cecc>] generic_file_fcntl+0xd7/0x140 Code: Bad EIP value. I am unable to explain this theory, but let me try: If I use my minimal .config that I used under vanilla 2.6.7-rc2 on FC2 kernel (2.6.5-1.358) and compile a custom kernel, then I do not see the crash. IOW there is some setting in the FC2's .config that upsets smbfs, which of course is not present in my custom .config. Alas, I am unable to identify what that is. (Initially I thought components like NLS and UTF-8 etc.. are to blame, but I proved myself wrong) If you want I can provide my custom .config in which I do not see any crashes (on both vanilla 2.6.7-rc2 and kernel built from FC2's 2.6.5-1.358 source). Hari My box is running FC2 release with latest updates. The smbfs crash problem still exists. It seems that the smbfs has conflict with nautilus. When I shut down nautilus, smbfs mounting will not crash: # su # rpm -e --nodeps nautilus # kill `/var/run/nautilus.pid` # mount //ictsamba/www /mnt/www -t smbfs -o user=henry Now my FC2 box has nautilus removed, and smbfs is working. (Crazy enough!?) Henry Leung from Hong Kong I reliably saw this bug with our corporate SMB servers (under Nautilus). Checking up on the state, I installed kernel-2.6.7-1.456 and mounted under both nautilus (Gnome session) and konqueror (KDE session). Still oopsed with nautilus, but mounted and worked well with konq. To make sure I'd file my backtrace dmesg with the latest software, I got arjans kernel-2.6.7-1.459 and tried again. Guess what. The oops is gone. No related entries in dmesg (Linux version 2.6.7-1.459 (bhcompile.redhat.com) (gcc version 3.4.0 20040621 (Red Hat Linux 3.4.0-7)) #1 Mon Jun 28 16:20:56 EDT 2004) either. The following patch, by Zwane Mwaikambo, titled "[PATCH] Fix smbfs readdir oops", which appeared in 2.6.7-bk11 solves the problem: http://linux.bkbits.net:8080/linux-2.5/cset@1.1844?nav=index.html|ChangeSet@-1d Thanks Hari PS: I have confirmed that the bug exists in 2.6.7-bk10; indeed, it is fixed in 2.6.7-bk11. This URL is recommened as a bookmarkable link: http://linux.bkbits.net:8080/linux-2.5/cset@40dfbc07ORT3D_k2q1d0pVZ6b4hZuQ?nav=index.html|ChangeSet@-1d Thanks Hari The 2.6.7-1.494.2.2 fedora core 2 kernel update, which was released few days ago, fixes the issue. Please refer to this article: Fedora Update Notification FEDORA-2004-247 2004-08-03 for more information. Thank you. Hari |