[Bug 764402] New: Latest Tumbleweed kernel update 3.3.6 to 3.4.0 breaks cifs-mounting my NAS
https://bugzilla.novell.com/show_bug.cgi?id=764402 https://bugzilla.novell.com/show_bug.cgi?id=764402#c0 Summary: Latest Tumbleweed kernel update 3.3.6 to 3.4.0 breaks cifs-mounting my NAS Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: i586 OS/Version: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: Samba AssignedTo: samba-maintainers@SuSE.de ReportedBy: dbischof@hrz.uni-kassel.de QAContact: samba-maintainers@SuSE.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20100101 Firefox/12.0 The latest Tumbleweed kernel update 3.3.6 to 3.4.0 breaks cifs-mounting my home-NAS (used to work flawlessly with 3.3.6 and before). Accessing the NAS with smbclient still works. After having rebooted the client machine with the current 12.1-Kernel (3.1.10), the problem no longer occurs (i'm aware that this is not an actual 12.1 bug (since i use Tumbleweed) but i was told to report it here). /etc/fstab excerpt --- //garcon/media /home/mediarw cifs nodfs,user,noauto,user=daniel,uid=daniel,gid=users,credentials=/home/daniel/.smbcredentials,iocharset=utf8,file_mode=0755,dir_mode=0755 0 0 --- verbose error messages in /var/log/messages --- [...] May 24 18:36:39 kernel: [ 5128.098432] CIFS VFS: Connecting to DFS root not implemented yet May 24 18:36:39 kernel: [ 5128.098550] /[...]/linux-3.4/fs/cifs/connect.c: CIFS VFS: leaving cifs_mount (xid = 17) rc = -22 May 24 18:36:39 kernel: [ 5128.098559] CIFS VFS: cifs_mount failed w/return code = -22 --- My NAS is running Samba 3.0.24. On my machine at work (same configuration as my machine at home = openSUSE 12.1/Tumbleweed), mounting a Samba share from a Samba server with a more recent Samba version (3.5.7) works flawlessly with kernel 3.4.0. Reproducible: Always Check http://lists.opensuse.org/opensuse-factory/2012-05/msg00571.html for further details. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c
Daniel Bischof
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c1
Suresh Jayaraman
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c
Suresh Jayaraman
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c2
--- Comment #2 from Daniel Bischof
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c3
Daniel Bischof
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c4
Rainer Klier
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c5
--- Comment #5 from Rainer Klier
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c6
--- Comment #6 from Daniel Bischof
Me too! i also updated kernel from 3.3.6 to 3.4.0. and i also get this mount error. but only on a share which is on a DFS: [...]
Hmm. My NAS (D-Link DNS-323) is running Linux. Isn't DFS a feature that is only available on Windows-Fileservers? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c7
Suresh Jayaraman
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c8
--- Comment #8 from Rainer Klier
Rainer: Can you also attach the network packet capture as mentioned above? Also
i did: tcpdump -s0 -w cifs-debug.cap 'port 137 || 138 || 139 || 445' this showed: tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes in another konsole id tried the failing mount again with: mount.cifs -o user=klier,pass=password //Tsdaten01/trosoft-dfs /mnt/bserver this showed the error: mount error(22): Invalid argument Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and dmesg showed: [ 7474.465920] CIFS VFS: Connecting to DFS root not implemented yet [ 7474.466252] CIFS VFS: cifs_mount failed w/return code = -22 after doing echo 3 > /proc/fs/cifs/cifsFYI the mount resulted in the following dmesg output: [ 7646.215327] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/cifsfs.c: Devname: //Tsdaten01/trosoft-dfs flags: 0 [ 7646.215349] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: Username: klier [ 7646.215353] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: file mode: 0x1ed dir mode: 0x1ed [ 7646.215436] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: CIFS VFS: in cifs_mount as Xid: 1064 with uid: 0 [ 7646.215440] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: UNC: \\Tsdaten01\trosoft-dfs ip: 172.16.17.3 [ 7646.215445] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: Existing tcp session with server found [ 7646.215448] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: CIFS VFS: in cifs_get_smb_ses as Xid: 1065 with uid: 0 [ 7646.215452] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: Existing smb sess found (status=1) [ 7646.215456] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: CIFS VFS: leaving cifs_get_smb_ses (xid = 1065) rc = 0 [ 7646.215462] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: CIFS VFS: in cifs_get_tcon as Xid: 1066 with uid: 0 [ 7646.215472] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/transport.c: For smb_command 117 [ 7646.215475] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/transport.c: Sending smb: total_len 102 [ 7646.215963] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: RFC1002 header 0x3e [ 7646.216038] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/transport.c: cifs_sync_mid_result: cmd=117 mid=909 state=4 [ 7646.216043] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: disk share connection [ 7646.216047] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: nativeFileSystem=NTFS [ 7646.216050] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: Tcon flags: 0x3 [ 7646.216054] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: CIFS VFS: leaving cifs_get_tcon (xid = 1066) rc = 0 [ 7646.216057] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: CIFS Tcon rc = 0 [ 7646.216060] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/cifssmb.c: In QFSDeviceInfo [ 7646.216064] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/transport.c: For smb_command 50 [ 7646.216067] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/transport.c: Sending smb: total_len 72 [ 7646.216383] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: RFC1002 header 0x40 [ 7646.216999] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/transport.c: cifs_sync_mid_result: cmd=50 mid=910 state=4 [ 7646.217009] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/cifssmb.c: In QFSAttributeInfo [ 7646.217027] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/transport.c: For smb_command 50 [ 7646.217029] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/transport.c: Sending smb: total_len 72 [ 7646.217242] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: RFC1002 header 0x4c [ 7646.217253] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/transport.c: cifs_sync_mid_result: cmd=50 mid=911 state=4 [ 7646.217257] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: build_unc_path_to_root: full_path=\\Tsdaten01\trosoft-dfs [ 7646.217261] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/cifssmb.c: In GetDFSRefer the path \Tsdaten01\trosoft-dfs [ 7646.217264] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/transport.c: For smb_command 50 [ 7646.217267] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/transport.c: Sending smb: total_len 120 [ 7646.217772] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: RFC1002 header 0xec [ 7646.217798] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/transport.c: cifs_sync_mid_result: cmd=50 mid=912 state=4 [ 7646.217803] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/cifssmb.c: Decoding GetDFSRefer response BCC: 181 Offset 56 [ 7646.217806] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/cifssmb.c: num_referrals: 1 dfs flags: 0x3 ... [ 7646.217807] [ 7646.217818] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/dns_resolve.c: dns_resolve_server_name_to_ip: resolved: Tsdaten01 to 172.16.17.3 [ 7646.217832] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: Username: klier [ 7646.217835] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: cifs_put_tcon: tc_count=1 [ 7646.217837] [ 7646.217839] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: CIFS VFS: in cifs_put_tcon as Xid: 1067 with uid: 0 [ 7646.217842] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/cifssmb.c: In tree disconnect [ 7646.217845] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/transport.c: For smb_command 113 [ 7646.217847] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/transport.c: Sending smb: total_len 39 [ 7646.218324] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: RFC1002 header 0x23 [ 7646.218334] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/transport.c: cifs_sync_mid_result: cmd=113 mid=913 state=4 [ 7646.218338] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: cifs_put_smb_ses: ses_count=7 [ 7646.218340] [ 7646.218342] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: CIFS VFS: leaving cifs_mount (xid = 1064) rc = 0 [ 7646.218345] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: CIFS VFS: in cifs_mount as Xid: 1068 with uid: 0 [ 7646.218348] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: UNC: (null) ip: (null) [ 7646.218350] CIFS VFS: Connecting to DFS root not implemented yet [ 7646.218430] /home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.0/linux-3.4/fs/cifs/connect.c: CIFS VFS: leaving cifs_mount (xid = 1068) rc = -22 [ 7646.218433] CIFS VFS: cifs_mount failed w/return code = -22 but no output was shown in the tcpdump konsole!
please try to go back to 3.3.6 and confirm whether you see the issue or not.
this i can't do, because 3.3.6 is not offered any more in any repo i know. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c9
--- Comment #9 from Suresh Jayaraman
i did:
tcpdump -s0 -w cifs-debug.cap 'port 137 || 138 || 139 || 445'
but no output was shown in the tcpdump konsole!
The "-w" option allows you to specify the output file. So, please attach cifs-debug.cap which is the output file with the captured packets in this case. I guess eth0 is the only network interface using via the client talks to the Server. If not you might have to use the option "-i <your-interface>" along with the other options. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c10
--- Comment #10 from Rainer Klier
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c11
--- Comment #11 from Rainer Klier
(In reply to comment #8)
i did:
tcpdump -s0 -w cifs-debug.cap 'port 137 || 138 || 139 || 445'
but no output was shown in the tcpdump konsole!
The "-w" option allows you to specify the output file. So, please attach
silly me. i am not using tcpdump frequently... ;-)
cifs-debug.cap which is the output file with the captured packets in this case.
ok.
I guess eth0 is the only network interface using via the client talks to the
yes. currently my computer is connected via eth0. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c12
--- Comment #12 from Daniel Bischof
To debug further, please attach the cifs network packet capture. Info on how to capture cifs packets can be found here (second bullet point) http://en.opensuse.org/openSUSE:Bugreport_Samba#Debugging_cifs_vfs_client
I'll do so and attach the output.
I haven't yet figured out why the problem is seen with 3.4.0. From your report I understand the problem was not seen with 3.3.6. We have just 2 cifs commits since 3.3.6 and both doesn't seem to be related.
Can you confirm whether mounting works fine if you go back to 3.3.6?
I can't go back to 3.3.6, since this kernel isn't available from the Tumbleweed repo anymore. However, as a workaround, I installed the 12.1 vanilla kernel package to have a boot option that allows me to access my NAS.
Also a few things to try to narrow down the issue:
1) Manually try mounting cifs with for e.g. mount -t cifs //server/share /mnt/point
2) I'm not sure why you use the mount options - nodfs, iocharset. Try leaving these options and see whether it works. Also instead of providing credentials file as a mount option, try providing "user=username, pass=password".
I haven't touched the mount options for years - frankly, I don't recall why I use them. I did, however, try to mount manually with a minimum set of options before I filed the bug. The behaviour is as follows: - Using Kernel 3.4.0 on the client ("daniel"): --- daniel:~ # mount -t cifs //garcon/media /home/mediarw -o user=daniel Password: mount error(22): Invalid argument Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) --- - Using the very same system, except having booted Kernel 3.1.10-1.9-vanilla --- daniel:~ # mount -t cifs //garcon/media /home/mediarw -o user=daniel Password: daniel:~ # mount [...] //garcon/media/ on /home/mediarw type cifs (rw,relatime,sec=ntlm,unc=\\garcon\media,username=daniel,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.42.13,file_mode=0755,dir_mode=0755,nounix,serverino,rsize=16384,wsize=131007,actimeo=1) --- For completeness, I'll attach the dmesg-output for the latter case.
What is the version of cifs-utils you are running (rpm -qa | grep cifs-utils)
--- daniel:~ # rpm -qa | grep cifs-utils cifs-utils-4.9-7.7.1.i586 --- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c13
--- Comment #13 from Daniel Bischof
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c14
Daniel Bischof
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c15
--- Comment #15 from Suresh Jayaraman
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c16
Suresh Jayaraman
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c17
--- Comment #17 from Daniel Bischof
[...] To figure out this I have a debug patch. If you know how to compile the kernel, could you please try applying this patch, enable cifs debugging and provide the debugging output?
It has been years since I had to compile a kernel... I'll try on Thursday (public holiday here). Could you please point me to some info on how to properly do this these days?
Also it would help to do a packet capture of 3.1.10 (working case) so that I can compare the dfs calls response between working and broken case. Thanks.
I will do so and create an attachment from the output.
How certain are you that it worked with 3.3.6? I know you can't go back, but is it that you started seeing the problem just after upgrading to 3.4 or there is a chance that 3.3.6 was not longer enough on the box to notice this issue?
I have to apologize here. I searched carefully through my syslog/zypper history and found the following: Kernel update history: 3.3.3 -> 3.3.4 : May, 02 3.3.4 -> 3.3.5 : May, 13 3.3.5 -> 3.3.6 : May, 19 3.3.6 -> 3.4.0 : May, 23 Last successful CIFS mount of my NAS, however, dates back to May, 17. So 3.3.6 _could_ have been broken already. 3.3.5 positively worked. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c18
--- Comment #18 from Daniel Bischof
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c19
--- Comment #19 from Suresh Jayaraman
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c20
Daniel Bischof
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c21
--- Comment #21 from Suresh Jayaraman
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c
Suresh Jayaraman
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c22
Daniel Bischof
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c23
Suresh Jayaraman
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c24
--- Comment #24 from Rainer Klier
same issue. I think this patch should for you too.
I'll push the patch to openSUSE repo once it gets accepted upstream. Thanks!
thank you for fixing this bug! when do you think, the fixed kernel will be available? and where? in http://ftp5.gwdg.de/pub/opensuse/repositories/Kernel:/HEAD/standard/ or http://ftp5.gwdg.de/pub/opensuse/repositories/Kernel:/stable/standard/ or http://ftp5.gwdg.de/pub/opensuse/repositories/openSUSE:/Tumbleweed/standard/ and how do we know the fix i built in? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c25
--- Comment #25 from Suresh Jayaraman
(In reply to comment #23)
same issue. I think this patch should for you too.
I'll push the patch to openSUSE repo once it gets accepted upstream. Thanks!
thank you for fixing this bug!
when do you think, the fixed kernel will be available? and where? in
I think it will be available both here (as it has been marked for -stable)
http://ftp5.gwdg.de/pub/opensuse/repositories/Kernel:/stable/standard/
and here
http://ftp5.gwdg.de/pub/opensuse/repositories/openSUSE:/Tumbleweed/standard/
and how do we know the fix i built in?
The easiest way is to check the kernel changelog rpm -q --changelog kernel-desktop-<yournewerversion> | less and look for this bug number and/or the changelog. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c26
--- Comment #26 from Rainer Klier
(In reply to comment #24)
(In reply to comment #23)
when do you think, the fixed kernel will be available? and where? in
I think it will be available both here (as it has been marked for -stable)
thanks for the fast reply.
and how do we know the fix i built in?
The easiest way is to check the kernel changelog rpm -q --changelog kernel-desktop-<yournewerversion> | less
and look for this bug number and/or the changelog.
ok, but for this, we will have to install it first. so i will first download the rpm and then look into it's changelog. thank you. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c27
Suresh Jayaraman
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c28
Paul M
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c29
--- Comment #29 from Rainer Klier
I have been burned by this bug - kernel 3.4.2-28-desktop using a windows file server.
the thing that confuses me is that I can mount some of the file shares off the replicating server, but not others, and I am not sure why the windows server shares are different.
because some of them may be DFSs, and others don't. this also happens to me. some of my mounted shares work, one does not. and this one is a DFS...... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c30
--- Comment #30 from Rainer Klier
Fix got merged into cifs maintainer's tree and should be available in upstream kernel 3.5-rc3. It has been marked for -stable so it should get into next stable and tumbleweed updates as well automatically (I cannot really say "when" because it depends on when tumbleweed/stable maintainers decide to do next update but it shouldn't be too long). The fix is not required for 12.1.
until today the patch isn't available in any of the above stated kernels. i checked the changlog from kernels 3.5.rc4 and 3.4.4. :-( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c31
--- Comment #31 from Daniel Bischof
https://bugzilla.novell.com/show_bug.cgi?id=764402
https://bugzilla.novell.com/show_bug.cgi?id=764402#c32
--- Comment #32 from Rainer Klier
Sureshs fix is in the latest Tumbleweed-Kernel 3.4.5-33 and works fine. Finally ;-)
yes, thanks. i already use it since the 3.4.5 kernel came out in Tumbleweed and Kernel:/stable/standard. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com