Activity log for bug #1746482

Date Who What changed Old value New value Message
2018-01-31 10:18:55 Dariusz Gadomski bug added bug
2018-01-31 10:30:04 Ubuntu Kernel Bot linux (Ubuntu): status New Incomplete
2018-01-31 10:30:06 Ubuntu Kernel Bot tags sts artful sts
2018-01-31 13:47:04 Dariusz Gadomski attachment added dmesg.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+attachment/5046387/+files/dmesg.txt
2018-01-31 17:16:15 Joseph Salisbury tags artful sts artful kernel-da-key needs-bisect sts
2018-01-31 17:16:26 Joseph Salisbury linux (Ubuntu): importance Undecided Medium
2018-02-02 10:24:40 Amad Ali bug added subscriber Amad Ali
2018-02-02 10:30:58 Dariusz Gadomski description On a Xenial installation after upgrading to the HWE 4.13.0-32-generic kernel it is not possible to use mount.cifs with -o vers=x.y different than 1.0. Steps to reproduce: 1. Setup a local Samba share. 2. Run: mount.cifs -o user=<myuser>,vers=2.0 //localhost/theshare/ /mnt/theshare (please note that not specifying the vers= option results in using protocol SMB2.1 which also results in the error). 3. This may be repeated for the following versions: 2.0, 2.1, 3.0. Expected result: The share gets mounted at /mnt/theshare. Actual result: The share is not mounted, this gets printed in the console (and in dmesg): [ 232.439162] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-2 On a Xenial installation after upgrading to the HWE 4.13.0-32-generic kernel it is not possible to use mount.cifs with -o vers=x.y different than 1.0. Steps to reproduce: 1. Setup a local Samba share. 2. Run: mount.cifs -o user=<myuser>,sec=ntlm //localhost/theshare/ /mnt/theshare (please note that not specifying the vers= option results in using protocol SMB2.1 which also results in the error). 3. This may be repeated for the following versions: 2.0, 2.1, 3.0. Expected result: The share gets mounted at /mnt/theshare. Actual result: The share is not mounted, this gets printed in the console (and in dmesg): [ 232.439162] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-2
2018-02-02 11:01:50 Dariusz Gadomski description On a Xenial installation after upgrading to the HWE 4.13.0-32-generic kernel it is not possible to use mount.cifs with -o vers=x.y different than 1.0. Steps to reproduce: 1. Setup a local Samba share. 2. Run: mount.cifs -o user=<myuser>,sec=ntlm //localhost/theshare/ /mnt/theshare (please note that not specifying the vers= option results in using protocol SMB2.1 which also results in the error). 3. This may be repeated for the following versions: 2.0, 2.1, 3.0. Expected result: The share gets mounted at /mnt/theshare. Actual result: The share is not mounted, this gets printed in the console (and in dmesg): [ 232.439162] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-2 On a Xenial installation after upgrading to the HWE 4.13.0-32-generic kernel it is not possible to use mount.cifs with -o vers=x.y different than 1.0. Steps to reproduce: 1. Setup a local Samba share with ntlm auth = yes. 2. Run: mount.cifs -o user=<myuser>,sec=ntlm,vers=2.0 //localhost/theshare/ /mnt/theshare 3. This may be repeated for the following versions: 2.0, 2.1, 3.0. Expected result: The share gets mounted at /mnt/theshare. Actual result: The share is not mounted, this gets printed in the console (and in dmesg): [ 232.439162] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-2
2018-02-02 11:05:49 Dariusz Gadomski description On a Xenial installation after upgrading to the HWE 4.13.0-32-generic kernel it is not possible to use mount.cifs with -o vers=x.y different than 1.0. Steps to reproduce: 1. Setup a local Samba share with ntlm auth = yes. 2. Run: mount.cifs -o user=<myuser>,sec=ntlm,vers=2.0 //localhost/theshare/ /mnt/theshare 3. This may be repeated for the following versions: 2.0, 2.1, 3.0. Expected result: The share gets mounted at /mnt/theshare. Actual result: The share is not mounted, this gets printed in the console (and in dmesg): [ 232.439162] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-2 On a Xenial installation after upgrading to the HWE 4.13.0-32-generic kernel it is not possible to use mount.cifs with -o vers=x.y different than 1.0. Steps to reproduce: 1. Setup a local Samba share with ntlm auth = yes. 2. Run: mount.cifs -o user=<myuser>,sec=ntlm,vers=2.0 //localhost/theshare/ /mnt/theshare 3. This may be repeated for the following versions: 2.0, 2.1, 3.0. Expected result: The share gets mounted at /mnt/theshare. Actual result: The share is not mounted, this gets printed in the console: mount error(22): Invalid argument Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and in dmesg: [ 61.935687] CIFS VFS: Unable to select appropriate authentication method! [ 61.935689] CIFS VFS: Send error in SessSetup = -22 [ 61.935744] CIFS VFS: cifs_mount failed w/return code = -22
2018-02-02 11:06:38 Dariusz Gadomski attachment added dmesg.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+attachment/5047510/+files/dmesg_latest.log
2018-02-02 11:07:04 Dariusz Gadomski attachment added dmesg.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+attachment/5047511/+files/dmesg_latest.log
2018-02-02 11:07:34 Dariusz Gadomski attachment removed dmesg.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+attachment/5046387/+files/dmesg.txt
2018-02-02 11:07:42 Dariusz Gadomski attachment removed dmesg.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+attachment/5047510/+files/dmesg_latest.log
2018-02-05 15:44:52 Dariusz Gadomski summary mount.cifs stopped working with protocol version != 1.0 mount.cifs stopped working with protocol version>1 and sec=ntlm
2018-03-25 00:07:16 Arnold Mendez bug added subscriber Arnold Mendez
2018-04-07 04:17:20 Launchpad Janitor linux (Ubuntu): status Incomplete Expired