Bug 704125
| Summary: | kernel-2.6.35.13-91 breaks mount.cifs | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Sandro Bonazzola <sandro.bonazzola> | ||||
| Component: | kernel | Assignee: | Jeff Layton <jlayton> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 14 | CC: | bdwheele, gansalmon, hansecke, itamar, jonathan, kernel-maint, madhu.chinakonda, steved | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | kernel-2.6.38.7-30.fc15 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-06-07 04:36:09 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: | |||||||
| Attachments: |
|
||||||
|
Description
Sandro Bonazzola
2011-05-12 08:37:08 UTC
What does the corresponding trace look like when it works in the older kernel? (In reply to comment #1) > What does the corresponding trace look like when it works in the older kernel? [ 569.252246] fs/cifs/cifsfs.c: Devname: //WIN98/DATA$/ flags: 0 [ 569.252335] fs/cifs/connect.c: CIFS VFS: in cifs_mount as Xid: 6 with uid: 0 [ 569.252358] fs/cifs/connect.c: Username: root [ 569.252364] fs/cifs/connect.c: UNC: \\WIN98\DATA$ ip: 10.0.0.3 [ 569.252379] fs/cifs/connect.c: Socket created [ 569.252969] fs/cifs/connect.c: sndbuf 16384 rcvbuf 87380 rcvtimeo 0x1b58 [ 569.252975] fs/cifs/transport.c: Sending smb: total_len 72 [ 569.254180] fs/cifs/connect.c: CIFS VFS: in cifs_get_smb_ses as Xid: 7 with uid: 0 [ 569.254187] fs/cifs/connect.c: Demultiplex PID: 4361 [ 569.254193] fs/cifs/connect.c: Existing smb sess not found [ 569.254200] fs/cifs/connect.c: rfc1002 length 0x82000004 [ 569.254204] fs/cifs/connect.c: Good RFC 1002 session rsp [ 569.254207] fs/cifs/cifssmb.c: secFlags 0x7 [ 569.254212] fs/cifs/transport.c: For smb_command 114 [ 569.254216] fs/cifs/transport.c: Sending smb: total_len 82 [ 569.254420] fs/cifs/connect.c: rfc1002 length 0x51 [ 569.254442] fs/cifs/cifssmb.c: Dialect: 2 [ 569.254446] fs/cifs/cifssmb.c: share mode security [ 569.254449] fs/cifs/cifssmb.c: negprot rc 0 [ 569.254453] fs/cifs/connect.c: Security Mode: 0x2 Capabilities: 0x203 TimeAdjust: -7200 [ 569.254457] fs/cifs/sess.c: sess setup type 2 [ 569.254573] fs/cifs/transport.c: For smb_command 115 [ 569.254577] fs/cifs/transport.c: Sending smb: total_len 182 [ 569.254734] fs/cifs/connect.c: rfc1002 length 0x2d [ 569.254753] fs/cifs/misc.c: Null buffer passed to cifs_small_buf_release [ 569.254758] fs/cifs/sess.c: ssetup rc from sendrecv2 is 0 [ 569.254761] fs/cifs/sess.c: UID = 0 [ 569.254764] fs/cifs/sess.c: decode sessetup ascii. bleft 0 [ 569.254768] fs/cifs/sess.c: ssetup freeing small buf f32cd880 [ 569.254772] fs/cifs/connect.c: CIFS Session Established successfully [ 569.254792] fs/cifs/connect.c: CIFS VFS: leaving cifs_get_smb_ses (xid = 7) rc = 0 [ 569.254797] fs/cifs/connect.c: file mode: 0x1ed dir mode: 0x1ed [ 569.254804] fs/cifs/connect.c: CIFS VFS: in cifs_get_tcon as Xid: 8 with uid: 0 [ 569.254913] fs/cifs/transport.c: For smb_command 117 [ 569.254917] fs/cifs/transport.c: Sending smb: total_len 98 [ 569.255124] fs/cifs/connect.c: rfc1002 length 0x2e [ 569.255474] fs/cifs/connect.c: nativeFileSystem= [ 569.255479] fs/cifs/connect.c: Tcon flags: 0x0 [ 569.255485] fs/cifs/connect.c: CIFS VFS: leaving cifs_get_tcon (xid = 8) rc = 0 [ 569.255489] fs/cifs/connect.c: CIFS Tcon rc = 0 [ 569.255493] fs/cifs/cifssmb.c: In QFSDeviceInfo [ 569.255500] fs/cifs/transport.c: For smb_command 50 [ 569.255505] fs/cifs/transport.c: Sending smb: total_len 72 [ 569.255745] fs/cifs/connect.c: rfc1002 length 0x27 [ 569.255754] fs/cifs/connect.c: invalid transact2 word count [ 569.255769] fs/cifs/netmisc.c: Mapping smb error code 64 to POSIX err -56 [ 569.255775] fs/cifs/cifssmb.c: Send error in QFSDeviceInfo = -56 [ 569.255780] fs/cifs/cifssmb.c: In QFSAttributeInfo [ 569.255786] fs/cifs/transport.c: For smb_command 50 [ 569.255791] fs/cifs/transport.c: Sending smb: total_len 72 [ 569.256100] fs/cifs/connect.c: rfc1002 length 0x52 [ 569.256121] fs/cifs/connect.c: CIFS VFS: leaving cifs_mount (xid = 6) rc = 0 [ 569.256129] fs/cifs/inode.c: CIFS VFS: in cifs_root_iget as Xid: 9 with uid: 0 [ 569.256135] fs/cifs/inode.c: Getting info on [ 569.256143] fs/cifs/transport.c: For smb_command 50 [ 569.256149] fs/cifs/transport.c: Sending smb: total_len 77 [ 569.256368] fs/cifs/connect.c: rfc1002 length 0x3e [ 569.256386] fs/cifs/netmisc.c: Mapping smb error code 1 to POSIX err -22 [ 569.256393] fs/cifs/cifssmb.c: Send error in QPathInfo = -22 [ 569.256398] fs/cifs/cifssmb.c: In SMBQPath path [ 569.256404] fs/cifs/transport.c: For smb_command 8 [ 569.256408] fs/cifs/transport.c: Sending smb: total_len 41 [ 569.256726] fs/cifs/connect.c: rfc1002 length 0x3b [ 569.256746] fs/cifs/inode.c: looking for uniqueid=119 [ 569.256754] fs/cifs/inode.c: cifs_revalidate_cache: revalidating inode 119 [ 569.256759] fs/cifs/inode.c: cifs_revalidate_cache: inode 119 is new [ 569.256765] fs/cifs/inode.c: inode 0xf3b201c8 old_time=0 new_time=270401 Same symptoms here. 2.6.35.12-90.fc14.i686 works fine, while 2.6.35.13-91.fc14.i686 produces the error. Happy to provide additional debug output, but surface symptoms are identical to Sandro's. My mount command line: mount -t cifs -o domain=mesoscopic,sec=lanman,servern=ABMM,password=,file_mode=0644,dir_mode=0755 //10.11.12.13/VNA_MS98_D /mnt/abmm_d Only one cifs patch went in 2.6.35.13: From 70945643722ffeac779d2529a348f99567fa5c33 Mon Sep 17 00:00:00 2001 From: Jeff Layton <jlayton> Date: Mon, 14 Mar 2011 13:48:08 -0400 Subject: cifs: always do is_path_accessible check in cifs_mount Created attachment 499169 [details]
patch -- add fallback in is_path_accessible for old servers
Does this patch fix the issue?
(In reply to comment #5) > Created attachment 499169 [details] > patch -- add fallback in is_path_accessible for old servers > > Does this patch fix the issue? Yes, the patch seems to fix the issue for me. The share seems to be mounted correctly, without any error message. Patch sent upstream and I cc'ed stable. It should make the stable series in the near future. Thanks Win98 PC died with a blue screen of death on TCPIP. On linux side the mount command said: mount error(11): Resource temporarily unavailable dmesg: [12430.427578] CIFS VFS: No response for cmd 50 mid 51 [12430.991378] CIFS VFS: No response for cmd 8 mid 52 [12445.959353] CIFS VFS: No response for cmd 114 mid 53 [12445.959374] CIFS VFS: cifs_read_super: get root inode failed [12466.921558] CIFS VFS: No response for cmd 114 mid 57 [12497.030240] CIFS VFS: No response to cmd 115 mid 62 [12497.030250] CIFS VFS: Send error in SessSetup = -11 [12497.030413] CIFS VFS: Send error in SessSetup = -11 [12497.030422] CIFS VFS: cifs_mount failed w/return code = -11 [12517.992427] CIFS VFS: No response for cmd 114 mid 64 [12538.954627] CIFS VFS: No response for cmd 114 mid 66 [12579.132707] CIFS VFS: No response for cmd 117 mid 70 [12600.093932] CIFS VFS: No response for cmd 114 mid 71 [12621.055078] CIFS VFS: No response for cmd 114 mid 73 [12642.017305] CIFS VFS: No response for cmd 114 mid 75 [12673.893174] CIFS VFS: No response to cmd 115 mid 78 [12673.893183] CIFS VFS: Send error in SessSetup = -11 It seems it doesn't work very well after all. This patch should fix the original problem. If Win98 is crashing, then there's not much we can do about it unless you can diagnose what's causing it. (In reply to comment #10) > This patch should fix the original problem. If Win98 is crashing, then there's > not much we can do about it unless you can diagnose what's causing it. I'll do more testing tomorrow in order to ensure it's a win98 problem and nothing related to the original problem. I can confirm it's a win98 problem and nothing related to the original problem. The patch works fine. Could you please add the patch to f14 stable kernel while we are waiting for a new upstream kernel stable release? The fix will be in 2.6.35.13-92 *** Bug 705644 has been marked as a duplicate of this bug. *** Is there something blocking 2.6.35.13-92 for update-testing? kernel-2.6.35.13-92.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/kernel-2.6.35.13-92.fc14 (In reply to comment #16) > kernel-2.6.35.13-92.fc14 has been submitted as an update for Fedora 14. > https://admin.fedoraproject.org/updates/kernel-2.6.35.13-92.fc14 It works for me. kernel-2.6.38.7-30.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/kernel-2.6.38.7-30.fc15 Package kernel-2.6.38.7-30.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-2.6.38.7-30.fc15' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/kernel-2.6.38.7-30.fc15 then log in and leave karma (feedback). kernel-2.6.38.7-30.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. kernel-2.6.35.13-92.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. |