From: "J. Bruce Fields" <bfields@fieldses.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-nfs@vger.kernel.org
Subject: nfsd fixes for 3.10
Date: Thu, 30 May 2013 20:47:48 -0400 [thread overview]
Message-ID: <20130531004748.GA14555@fieldses.org> (raw)
Please pull nfsd fixes for 3.10:
git://linux-nfs.org/~bfields/linux.git for-3.10
A couple minor fixes for the (new to 3.10) gss-proxy code.
And one regression from user-namespace changes. (XBMC clients were
doing something admittedly weird--sending -1 gid's--but something that
we used to allow.)
--b.
----------------------------------------------------------------
Dan Carpenter (1):
svcauth_gss: fix error code in use_gss_proxy()
J. Bruce Fields (2):
svcrpc: implement O_NONBLOCK behavior for use-gss-proxy
svcrpc: fix failures to handle -1 uid's and gid's
net/sunrpc/auth_gss/svcauth_gss.c | 8 +++++---
net/sunrpc/svcauth_unix.c | 12 +++++++-----
2 files changed, 12 insertions(+), 8 deletions(-)
reply other threads:[~2013-05-31 0:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130531004748.GA14555@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.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).