linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: samba-bugs@samba.org
To: cifs-qa@samba.org
Subject: [Bug 14521] New: CIFS mount shows only "vers=default" instead of specific SMB version
Date: Mon, 05 Oct 2020 17:31:31 +0000	[thread overview]
Message-ID: <bug-14521-10630@https.bugzilla.samba.org/> (raw)

https://bugzilla.samba.org/show_bug.cgi?id=14521

            Bug ID: 14521
           Summary: CIFS mount shows only "vers=default" instead of
                    specific SMB version
           Product: CifsVFS
           Version: 4.x
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5
         Component: kernel fs
          Assignee: sfrench@samba.org
          Reporter: kolAflash@kolahilft.de
        QA Contact: cifs-qa@samba.org
  Target Milestone: ---

/proc/mounts and the mount command don't show the auto negotiated version after
mounting with vers=default (or without specifying vers=).
Instead /proc/mounts just says vers=default.
Client OS: openSUSE-LEAP-15.2 with Linux-5.3

This non-public bug seems to be similar.
(I don't habe a RedHat license, so I can't see the details)
https://access.redhat.com/solutions/4592681

I was only able to reproduce with Windows Server 2012.
A Windows Server 2008 and Samba-4.6 (openSUSE-LEAP-42.3) work fine.
(e.g. /proc/mounts shows vers=3.11)


Workaround with some help from:
https://wiki.samba.org/index.php/LinuxCIFS_troubleshooting

echo 'module cifs +p' > /sys/kernel/debug/dynamic_debug/control
echo 'file fs/cifs/* +p' > /sys/kernel/debug/dynamic_debug/control
echo 7 > /proc/fs/cifs/cifsFYI
mount -t cifs ...
dmesg | grep -E 'cifs.*[123]\.[0-9]'
# -> negotiated smb3.02 dialect

So for me it's actually 3.02 what's been negotiated with Windows Server 2012.


P.S.
"man mount.cifs" may seem a little ambiguous about the vers=default behavior.
Quote:
==========
SMB protocol version. Allowed values are:
[...]
  - default - Tries to negotiate the highest SMB2+ version supported by both
the client and server.
[...]
  The default since v4.13.5 is for the client and server to negotiate
  the highest possible version greater than or equal to ``2.1``. In
  kernels prior to v4.13, the default was ``1.0``. For kernels
  between v4.13 and v4.13.5 the default is ``3.0``.
==========
The first one sound more like 2.0 <= vers < 3.0.
While the second sounds more like 2.1 <= version (without upper limit).
To me it looks like the second (2.1 <= version) is what's actually implemented
(at least with Linux-5.3 on openSUSE-LEAP-15.2).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

             reply	other threads:[~2020-10-05 17:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-05 17:31 samba-bugs [this message]
2020-10-06  9:01 ` [Bug 14521] CIFS mount shows only "vers=default" instead of specific SMB version samba-bugs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-14521-10630@https.bugzilla.samba.org/ \
    --to=samba-bugs@samba.org \
    --cc=cifs-qa@samba.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).