From: Jeff Layton <jlayton-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Pavel Shilovsky <piastryyy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-cifs <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Ronnie Sahlberg"
<lsahlber-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
"Aurélien Aptel" <aaptel-IBi9RG/b67k@public.gmane.org>,
"Pavel Shilovskiy"
<pshilov-0li6OtcxBFHby3iVrkZq2A@public.gmane.org>
Subject: Re: [cifs-utils PATCH v3] manpage: update mount.cifs manpage with info about default version being mounted
Date: Sun, 05 Nov 2017 08:35:42 -0500 [thread overview]
Message-ID: <1509888942.4773.6.camel@kernel.org> (raw)
In-Reply-To: <CAKywueRMN0-NfUVsBra+wRCsA0N8jwG+J3FqQUt5K18favSA=Q@mail.gmail.com>
On Sat, 2017-11-04 at 18:27 -0700, Pavel Shilovsky wrote:
> 2017-11-04 13:51 GMT-07:00 Jeff Layton <jlayton-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>:
> > From: Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
> >
> > Signed-off-by: Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
> > ---
> > mount.cifs.rst | 7 +++++--
> > 1 file changed, 5 insertions(+), 2 deletions(-)
> >
> > diff --git a/mount.cifs.rst b/mount.cifs.rst
> > index 9714f795fe76..499b9a778927 100644
> > --- a/mount.cifs.rst
> > +++ b/mount.cifs.rst
> > @@ -517,7 +517,7 @@ prefixpath=arg
> > vers=arg
> > SMB protocol version. Allowed values are:
> >
> > - - 1.0 - The classic CIFS/SMBv1 protocol. This is the default.
> > + - 1.0 - The classic CIFS/SMBv1 protocol.
> > - 2.0 - The SMBv2.002 protocol. This was initially introduced in
> > Windows Vista Service Pack 1, and Windows Server 2008. Note that
> > the initial release version of Windows Vista spoke a slightly
> > @@ -529,6 +529,10 @@ vers=arg
> > Note too that while this option governs the protocol version used, not
> > all features of each version are available.
> >
> > + In kernels v4.13.5 and later, the client and server negotiate a version
> > + greater than or equal to ``2.1``. In kernels prior to v4.13.5, the default
> > + is ``1.0``.
>
> Between v4.13 and v4.13.4 (included) the default is 3.0, not sure if
> we should be so precise here.
>
Grumble...the merge of that feature outside the normal merge window
makes this difficult to document. How about this?
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``.
It's still awkward, but I think it's correct.
> > +
> > --verbose
> > Print additional debugging information for the mount. Note that this
> > parameter must be specified before the ``-o`` . For example::
> > @@ -857,4 +861,3 @@ Steve French
> > The maintainer of the Linux cifs vfs and the userspace tool mount.cifs
> > is Steve French. The Linux CIFS Mailing list is the preferred place to
> > ask questions regarding these programs.
> > -
> > \ No newline at end of file
> > --
> > 2.13.6
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-cifs" in
> > the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
> --
> Best regards,
> Pavel Shilovsky
--
Jeff Layton <jlayton-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
next prev parent reply other threads:[~2017-11-05 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 20:51 [cifs-utils PATCH v3] manpage: update mount.cifs manpage with info about default version being mounted Jeff Layton
[not found] ` <20171104205151.3507-1-jlayton-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-11-05 1:27 ` Pavel Shilovsky
2017-11-05 13:35 ` Jeff Layton [this message]
[not found] ` <1509888942.4773.6.camel-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-11-05 18:06 ` Pavel Shilovsky
[not found] ` <CAKywueQ+NGsmvzg6Mcn41rKFGHcyM+AXurQbKdZSMCw4JJw_mg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-08 0:04 ` Jeff Layton
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=1509888942.4773.6.camel@kernel.org \
--to=jlayton-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=aaptel-IBi9RG/b67k@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lsahlber-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=piastryyy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=pshilov-0li6OtcxBFHby3iVrkZq2A@public.gmane.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