From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: ben@decadent.org.uk
Cc: sfrench@samba.org, linux-cifs@vger.kernel.org,
samba-technical@lists.samba.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: [v3.2.y][PATCH 0/1] cifs: set MAY_SIGN when sec=krb5
Date: Fri, 28 Feb 2014 16:07:34 -0500 [thread overview]
Message-ID: <cover.1393535604.git.joseph.salisbury@canonical.com> (raw)
BugLink: http://bugs.launchpad.net/bugs/1285723
Hi Ben,
Please consider including a backport of upstream commit 0b7bc84000d71f3647ca33ab1bf5bd928535c846 in the next v3.2.y release. It was included upstream as of v3.9-rc1. It has been tested and confirmed to resolve http://bugs.launchpad.net/bugs/1285723 .
commit 0b7bc84000d71f3647ca33ab1bf5bd928535c846
Author: Martijn de Gouw <martijn.de.gouw@prodrive.nl>
Date: Wed Oct 24 11:45:46 2012 +0200
cifs: set MAY_SIGN when sec=krb5
This commit has a requrement for commit 8830d7e07a5e38bc47650a7554b7c1cfd49902bf, so it does not apply cleanly to v3.2. I performed a backport to avoid this requirement, which is in email 1/1.
Sincerely,
Joseph Salisbury
Joseph Salisbury (1):
cifs: set MAY_SIGN when sec=krb5
fs/cifs/connect.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--
1.7.9.5
next reply other threads:[~2014-02-28 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 21:07 Joseph Salisbury [this message]
[not found] ` <cover.1393535604.git.joseph.salisbury-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2014-02-28 21:07 ` [v3.2.y][PATCH 1/1] cifs: set MAY_SIGN when sec=krb5 Joseph Salisbury
2014-03-30 20:34 ` Ben Hutchings
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=cover.1393535604.git.joseph.salisbury@canonical.com \
--to=joseph.salisbury@canonical.com \
--cc=ben@decadent.org.uk \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=sfrench@samba.org \
--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).