All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Aurélien Aptel" <aaptel@suse.com>
Cc: smfrench@gmail.com, pshilov@microsoft.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] SMB3: Fix length checking of SMB3.11 negotiate request" failed to apply to 4.16-stable tree
Date: Fri, 20 Apr 2018 16:58:37 +0200	[thread overview]
Message-ID: <20180420145837.GA27481@kroah.com> (raw)
In-Reply-To: <87zi1yb1v6.fsf@suse.com>

On Fri, Apr 20, 2018 at 12:37:01PM +0200, Aur�lien Aptel wrote:
> gregkh@linuxfoundation.org writes:
> > The patch below does not apply to the 4.16-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> 
> Backport of that particular patch was simple: the original patch assumes
> ronnie's header_preamble_size are in, with 4s changed to
> header_preamble_size. I just kept the 4s to fix the conflict.
> 
> But SMB3.11 is broken on this branch as signing is mandatory in 3.11 and
> it needs the preauth integrity patches. I get ACCESS_DENIED on
> TreeConnect against samba and signing failures against Windows Server
> 2016.
> 
> So until we also backport these, this patch is not very useful.
> 
> Here's the backport anyway if you want to apply it:

Sounds like I do not want it.  If someone could send me a proper patch
series of all of these patches that failed to apply, that would be much
more helpful.

thanks,

greg k-h

      reply	other threads:[~2018-04-20 14:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20  8:24 FAILED: patch "[PATCH] SMB3: Fix length checking of SMB3.11 negotiate request" failed to apply to 4.16-stable tree gregkh
2018-04-20 10:37 ` Aurélien Aptel
2018-04-20 14:58   ` Greg KH [this message]

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=20180420145837.GA27481@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=aaptel@suse.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.