stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pavel Shilovskiy <pshilov@microsoft.com>
Cc: Stable <stable@vger.kernel.org>, Steve French <smfrench@gmail.com>
Subject: Re: [PATCH] CIFS: Remove encryption from the capabilities flags
Date: Tue, 11 Apr 2017 05:41:42 +0200	[thread overview]
Message-ID: <20170411034142.GA28032@kroah.com> (raw)
In-Reply-To: <DM5PR03MB255315E59143B95CAD0F438DB6010@DM5PR03MB2553.namprd03.prod.outlook.com>

On Mon, Apr 10, 2017 at 09:29:41PM +0000, Pavel Shilovskiy wrote:
> On Mon, Feb 27, 2017 at 5:20 PM, Pavel Shilovsky <pshilov@microsoft.com> wrote:
> > Currently the client claims to support encryption but it doesn't.
> > This results in rejecting TreeConnect requests by a server that 
> > expects them to be encrypted. Fix it by removing encryption from the 
> > capabilities flags. This problem affects kernels from v4.5 to v4.10.
> >
> > Cc: Steve French <smfrench@gmail.com>
> > Cc: Stable <stable@vger.kernel.org> # v4.5-v4.10
> > Signed-off-by: Pavel Shilovsky <pshilov@microsoft.com>
> > ---
> >  fs/cifs/smb2ops.c | 8 ++++++--
> >  1 file changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/fs/cifs/smb2ops.c b/fs/cifs/smb2ops.c index 
> > 5d456eb..87a58f0 100644
> > --- a/fs/cifs/smb2ops.c
> > +++ b/fs/cifs/smb2ops.c
> > @@ -1925,7 +1925,9 @@ struct smb_version_values smb21_values = {  
> > struct smb_version_values smb30_values = {
> >         .version_string = SMB30_VERSION_STRING,
> >         .protocol_id = SMB30_PROT_ID,
> > -       .req_capabilities = SMB2_GLOBAL_CAP_DFS | SMB2_GLOBAL_CAP_LEASING | SMB2_GLOBAL_CAP_LARGE_MTU | SMB2_GLOBAL_CAP_PERSISTENT_HANDLES | SMB2_GLOBAL_CAP_ENCRYPTION,
> > +       .req_capabilities = SMB2_GLOBAL_CAP_DFS | SMB2_GLOBAL_CAP_LEASING
> > +                       | SMB2_GLOBAL_CAP_LARGE_MTU
> > +                       | SMB2_GLOBAL_CAP_PERSISTENT_HANDLES,
> >         .large_lock_type = 0,
> >         .exclusive_lock_type = SMB2_LOCKFLAG_EXCLUSIVE_LOCK,
> >         .shared_lock_type = SMB2_LOCKFLAG_SHARED_LOCK, @@ -1945,7 
> > +1947,9 @@ struct smb_version_values smb30_values = {  struct 
> > smb_version_values smb302_values = {
> >         .version_string = SMB302_VERSION_STRING,
> >         .protocol_id = SMB302_PROT_ID,
> > -       .req_capabilities = SMB2_GLOBAL_CAP_DFS | SMB2_GLOBAL_CAP_LEASING | SMB2_GLOBAL_CAP_LARGE_MTU | SMB2_GLOBAL_CAP_PERSISTENT_HANDLES | SMB2_GLOBAL_CAP_ENCRYPTION,
> > +       .req_capabilities = SMB2_GLOBAL_CAP_DFS | SMB2_GLOBAL_CAP_LEASING
> > +                       | SMB2_GLOBAL_CAP_LARGE_MTU
> > +                       | SMB2_GLOBAL_CAP_PERSISTENT_HANDLES,
> >         .large_lock_type = 0,
> >         .exclusive_lock_type = SMB2_LOCKFLAG_EXCLUSIVE_LOCK,
> >         .shared_lock_type = SMB2_LOCKFLAG_SHARED_LOCK,
> > --
> > 2.7.4
> >
> 
> Do you have any update on this patch? It seems suitable at least for 4.9 and 4.10 kernels.

What was the commit id for this in Linus's tree?  Did you read
Documentation/stable_kernel_rules.txt for how to get something merged
into a stable kernel?

If this isn't in Linus's tree, I need a whole lot of text explaining
that, and some signed-off-by from the maintainers.  None of which
happened here, which is why it is long gone from my patch queue.

thanks,

greg k-h

  reply	other threads:[~2017-04-11  3:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27 23:20 [PATCH] CIFS: Remove encryption from the capabilities flags Pavel Shilovsky
2017-02-27 23:32 ` Steve French
2017-04-10 21:29   ` Pavel Shilovskiy
2017-04-11  3:41     ` Greg Kroah-Hartman [this message]
2017-04-11  4:04       ` Steve French
2017-04-11  4:15         ` Greg Kroah-Hartman

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=20170411034142.GA28032@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=pshilov@microsoft.com \
    --cc=smfrench@gmail.com \
    --cc=stable@vger.kernel.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).