Launchpad has imported 13 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=196891.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2017-09-10T18:59:10+00:00 jed-kernel.org wrote: Ever since updating to 4.12.10, I have been getting "File name too long" messages when accessing my CIFS share: $ ls /nfs/users/test ls: cannot access '/nfs/users/test': File name too long On my system, the CIFS share is mounted on /nfs/users. (An NFS export was transitioned to CIFS a while back, hence the oddly named mount point.) This issue goes away if I revert to 4.12.8. Commit d3edede looks relevant. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/0 ------------------------------------------------------------------------ On 2017-09-13T21:58:12+00:00 lsahlber wrote: Which architecture do you see this on? Can you attach a network trace including the initial mount, i.e. the query calls where cifs.ko will discover what the maximum length the server supports during the mount. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/1 ------------------------------------------------------------------------ On 2017-09-14T04:22:44+00:00 lsahlber wrote: Please also try v4.13 as it contains the change 6e3c1529c39e92ed64ca41d53abadabbaa1d5393 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/2 ------------------------------------------------------------------------ On 2017-09-14T05:24:15+00:00 jed-kernel.org wrote: Created attachment 258363 CIFS queries and responses during mount Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/3 ------------------------------------------------------------------------ On 2017-09-14T05:30:35+00:00 jed-kernel.org wrote: Both server and client are x86_64. Server is samba 4.6.7. I've attached a trace excerpt showing the queries and responses during mount. The very last message shows the server responding with max length 255. The issue persists with 4.12.12, which includes 77ab9e7fb4312d3b377690660f757d900fa9e171, which I believe is the same as the change you mention above. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/4 ------------------------------------------------------------------------ On 2017-09-14T05:46:38+00:00 lsahlber wrote: That is SMB1. Can you try with a SMB2 mount too? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/5 ------------------------------------------------------------------------ On 2017-09-14T15:01:16+00:00 jed-kernel.org wrote: Created attachment 258383 SMB2.0 fs attr info query & response Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/6 ------------------------------------------------------------------------ On 2017-09-14T15:01:39+00:00 jed-kernel.org wrote: Created attachment 258385 SMB2.1 fs attr info query & response Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/7 ------------------------------------------------------------------------ On 2017-09-14T15:01:57+00:00 jed-kernel.org wrote: Created attachment 258387 SMB3.0 fs attr info query & response Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/8 ------------------------------------------------------------------------ On 2017-09-14T15:04:28+00:00 jed-kernel.org wrote: Same result with SMB2.0, SMB2.1, and SMB3.0. I've attached traces of the FileFsAttributeInformation queries and responses for all three protocol versions. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/9 ------------------------------------------------------------------------ On 2017-09-18T23:40:09+00:00 lsahlber wrote: I can not reproduce this issue using current linux/master branch. The queries look sane in the network trace so ... What fileserver are you using? Windows or Samba? And what version. Can you try using the same kernel and try accessing a different share on a different file server to see if things are different. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/10 ------------------------------------------------------------------------ On 2017-10-21T14:50:56+00:00 jed-kernel.org wrote: The server is Samba 4.6.7. Users are stored in LDAP and authenticated with Kerberos. Here are the mount options I am using: user=machine-root,multiuser,sec=krb5,x-systemd.automount Unfortunately, I don't have a different file server to play with, but I suspect it is the 'multiuser' option that is breaking things. Here are the contents of /proc/fs/cifs/DebugData after the initial mount: Display Internal CIFS Data Structures for Debugging --------------------------------------------------- CIFS Version 2.09 Features: dfs fscache posix spnego xattr acl Active VFS Requests: 0 Servers: Number of credits: 17 1) entry for SERVER_IP not fully displayed TCP status: 1 Local Users To Server: 1 SecMode: 0x1 Req On Wire: 0 Shares: 1) \\SERVER_NAME\users Mounts: 1 DevInfo: 0x20 Attributes: 0x1006f PathComponentMax: 255 Status: 1 type: DISK Share Capabilities: None Aligned, Partition Aligned, Share Flags: 0x0 Optimal sector size: 0x200 MIDs: And here it is again after I try to `ls /nfs/users/test` as a normal user: Display Internal CIFS Data Structures for Debugging --------------------------------------------------- CIFS Version 2.09 Features: dfs fscache posix spnego xattr acl Active VFS Requests: 0 Servers: Number of credits: 20 1) entry for SERVER_IP not fully displayed TCP status: 1 Local Users To Server: 2 SecMode: 0x1 Req On Wire: 0 Shares: 1) \\SERVER_NAME\users Mounts: 1 DevInfo: 0x0 Attributes: 0x0 PathComponentMax: 0 Status: 1 type: 0 Share Capabilities: None Share Flags: 0x0 MIDs: 1) entry for SERVER_IP not fully displayed TCP status: 1 Local Users To Server: 2 SecMode: 0x1 Req On Wire: 0 Shares: 1) \\SERVER_NAME\users Mounts: 1 DevInfo: 0x20 Attributes: 0x1006f PathComponentMax: 255 Status: 1 type: DISK Share Capabilities: None Aligned, Partition Aligned, Share Flags: 0x0 Optimal sector size: 0x200 MIDs: Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/15 ------------------------------------------------------------------------ On 2017-12-03T19:41:45+00:00 jed-kernel.org wrote: This is fixed with 4.14.3. I'm guessing f74bc7c6679200a4a83156bb89cbf6c229fe8ec0 is what did it. Thanks! Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725322/comments/21 ** Changed in: linux Status: Unknown => Fix Released ** Changed in: linux Importance: Unknown => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1725322 Title: kernel 4.4.0.97.102 breaks DFS Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu Desktop 16.04.3 We connect to Windows DFS using automounter with our Linux 16.04 workstations to let users access the windows shares. Until kernel version 4.4.0-96 this worked without any issues. However if a computer updates to kernel 4.4.0.97.102, using the same configs and samba version, it stops working and reports a "ls: cannot access xx: File name too long" error. (where xx is a foldername) Also if you run "ls -all" you will see: d????????? ? ? ? ? ? Applications on the same computer selecting kernel 4.4.0.21.22 at grub menu: drwx--x--x 2 root root 0 Oct 20 16:44 Applications Mount commando output (removed hostnames and IP numbers ) on computer with kernel 4.4.0.21.22 //XXX/Public on /vol/winshare/Public type cifs (rw,relatime,vers=1.0,sec=krb5,cache=strict,multiuser,uid=0,noforceuid,gid=0,noforcegid,addr=x.x.x.x file_mode=0755,dir_mode=0755,nounix,mapposix,noperm,rsize=61440,wsize=65536,actimeo=1) Mount commando output (removed hostnames and IP numbers ) on the same computer with kernel 4.4.0.97.102 //XXX/Public on /vol/winshare/Public type cifs (rw,relatime,vers=1.0,sec=krb5,cache=strict,multiuser,uid=0,noforceuid,gid=0,noforcegid,addr=x.x.x.x,file_mode=0755,dir_mode=0755,nounix,mapposix,noperm,rsize=61440,wsize=65536,echo_interval=60,actimeo=1) During these tests the only thing that changed is the running kernel, no other changes were applied. autofs config file used for this connection Public -fstype=cifs,sec=krb5,multiuser,nounix,noserverino ://<servername>/Public To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1725322/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
