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
** 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/theshar
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
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/+atta
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 specifi
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 t
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 i
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 => Med
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, w
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
10 matches
Mail list logo