[Kernel-packages] [Bug 1746482] Re: mount.cifs stopped working with protocol version != 1.0
Bisecting between v4.10 and v4.11 resulted in finding that this was caused by the following commit: [ef65aaede23f75977af56a8c330bb9be8c6e125c] smb2: Enforce sec= mount option Reverting it on top of v4.11 makes it go away. Looking more into it. -- 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/1746482 Title: mount.cifs stopped working with protocol version != 1.0 Status in linux package in Ubuntu: Incomplete Bug 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=,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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+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
[Kernel-packages] [Bug 1746482] Re: mount.cifs stopped working with protocol version != 1.0
** Description changed: 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=,vers=2.0 //localhost/theshare/ /mnt/theshare + mount.cifs -o user=,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 -- 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/1746482 Title: mount.cifs stopped working with protocol version != 1.0 Status in linux package in Ubuntu: Incomplete Bug 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=,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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+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
[Kernel-packages] [Bug 1746482] Re: mount.cifs stopped working with protocol version != 1.0
Conclusion after correcting the parameters in my test procedure: v4.10 - good v4.11 - bad v4.15 - bad I'm performing a bisect between v4.10 and v4.11. -- 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/1746482 Title: mount.cifs stopped working with protocol version != 1.0 Status in linux package in Ubuntu: Incomplete Bug 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=,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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+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
[Kernel-packages] [Bug 1746482] Re: mount.cifs stopped working with protocol version != 1.0
Added updated dmesg (with verbose error message). ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+attachment/5047511/+files/dmesg_latest.log ** Attachment removed: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+attachment/5046387/+files/dmesg.txt ** Attachment removed: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+attachment/5047510/+files/dmesg_latest.log -- 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/1746482 Title: mount.cifs stopped working with protocol version != 1.0 Status in linux package in Ubuntu: Incomplete Bug 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=,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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+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
[Kernel-packages] [Bug 1746482] Re: mount.cifs stopped working with protocol version != 1.0
Looks like I've been mislead by the man page of mount.cifs and
linux/fs/cifs/connect.c which state:
man mount.cifs:
vers=
SMB protocol version. Allowed values are:
ยท 1.0 - The classic CIFS/SMBv1 protocol. This is the
default.
4.13 kernel code:
pr_warn("No dialect specified on mount. Default has changed to "
"a more secure dialect, SMB2.1 or later (e.g. SMB3),
from CIFS "
"(SMB1). To use the less secure SMB1 dialect to access "
"old servers which do not support SMB3 (or SMB2.1)
specify vers=1.0"
" on mount.\n");
So looks like I need to explicitly apply the version number to
mount.cifs argument to have consistent results.
More over sec=ntlm is needed in smb.conf and mount.cifs cmdline.
Updating the description.
** Description changed:
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.
+ 1. Setup a local Samba share with ntlm auth = yes.
2. Run:
- mount.cifs -o user=,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).
+ mount.cifs -o user=,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
** Description changed:
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=,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
+ 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
--
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/1746482
Title:
mount.cifs stopped working with protocol version != 1.0
Status in linux package in Ubuntu:
Incomplete
Bug 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=,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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+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
[Kernel-packages] [Bug 1746482] Re: mount.cifs stopped working with protocol version != 1.0
Added updated dmesg (with verbose error message). ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+attachment/5047510/+files/dmesg_latest.log -- 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/1746482 Title: mount.cifs stopped working with protocol version != 1.0 Status in linux package in Ubuntu: Incomplete Bug 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=,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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+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
[Kernel-packages] [Bug 1746482] Re: mount.cifs stopped working with protocol version != 1.0
Surprisingly it works perfectly fine for 4.15.0-041500-generic. I have tested vers= parameter from 1.0 to 3.0 - no issues at all. I went forward and tested v4.14 - it is not affected by the issue as well. -- 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/1746482 Title: mount.cifs stopped working with protocol version != 1.0 Status in linux package in Ubuntu: Incomplete Bug 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=,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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+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
[Kernel-packages] [Bug 1746482] Re: mount.cifs stopped working with protocol version != 1.0
Can you see if this bug has been fixed in the latest mainline kernel: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/ If the bug still exists in 4.15, we can bisect between 4.12 and 4.13. ** Tags added: kernel-da-key needs-bisect ** Changed in: linux (Ubuntu) Importance: Undecided => 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/1746482 Title: mount.cifs stopped working with protocol version != 1.0 Status in linux package in Ubuntu: Incomplete Bug 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=,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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+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
[Kernel-packages] [Bug 1746482] Re: mount.cifs stopped working with protocol version != 1.0
dmesg output after reproducing the issue with echo 7 > /proc/fs/cifs/cifsFYI ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+attachment/5046387/+files/dmesg.txt -- 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/1746482 Title: mount.cifs stopped working with protocol version != 1.0 Status in linux package in Ubuntu: Incomplete Bug 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=,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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+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
[Kernel-packages] [Bug 1746482] Re: mount.cifs stopped working with protocol version != 1.0
As discussed with cascardo I tested the mainline builds from [1]. After some tests the results were: v4.12.14 - good v4.13 - bad So the regression seems to be introduced in v4.13. [1] http://kernel.ubuntu.com/~kernel-ppa/mainline/ -- 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/1746482 Title: mount.cifs stopped working with protocol version != 1.0 Status in linux package in Ubuntu: Incomplete Bug 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=,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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+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
