From: Jeff Layton <jlayton@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: stable@kernel.org, linux-cifs@vger.kernel.org,
linux-kernel@vger.kernel.org, helge.hafting@hist.no
Subject: Re: [stable] [PATCH] cifs: fix wsize negotiation for 2.6.39 stable
Date: Wed, 13 Jul 2011 06:44:04 -0400 [thread overview]
Message-ID: <20110713064404.668d42a5@tlielax.poochiereds.net> (raw)
In-Reply-To: <20110713022619.GA11043@kroah.com>
On Wed, 13 Jul 2011 04:26:19 +0200
Greg KH <greg@kroah.com> wrote:
> On Tue, Jul 12, 2011 at 09:24:41PM -0400, Jeff Layton wrote:
> > I sent this a week or so ago, but it apparently missed the recent
> > 2.6.39.y release. Resending to make sure it gets into the next one.
> >
> > Prior to 2.6.39, when signing was enabled on a socket the client only
> > sent single-page writes. This changed with commit ca83ce3d5b, which
> > made signed and unsigned connections use the same codepaths for write
> > calls.
> >
> > This caused a regression when working with windows servers. Windows
> > machines will reject writes larger than the MaxBufferSize when signing
> > is active, but does not clear the CAP_LARGE_WRITE_X flag in the
> > negotiation.
> >
> > This patch backports 2 patches that fix this problem in 3.0 kernels,
> > and changes a couple of the constants to values appropriate for the
> > writeback code in 2.6.39.
>
> Why not just tell me the 2 patches in upstream that need to be
> backported as Documentation/stable_kernel_rules.txt say to do instead?
>
> thanks,
>
> greg k-h
Ok, we can do it that way instead. I just sent a patch to
stable@kernel.org that alters the constants after listing the upstream
patches as prerequisites.
Unfortunately, we cannot simply cherry-pick the upstream patches to fix
this. 3.0 added support for much larger wsize= values in cifs, and we
have to account for that difference in 2.6.39.y.
Thanks,
--
Jeff Layton <jlayton@redhat.com>
prev parent reply other threads:[~2011-07-13 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 1:24 Jeff Layton
2011-07-13 2:26 ` [stable] " Greg KH
2011-07-13 10:44 ` Jeff Layton [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=20110713064404.668d42a5@tlielax.poochiereds.net \
--to=jlayton@redhat.com \
--cc=greg@kroah.com \
--cc=helge.hafting@hist.no \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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
all inboxes | Powered by JetHome®