From: "J. Bruce Fields" <bfields@fieldses.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] nfsd bugfixes for 3.18
Date: Tue, 25 Nov 2014 18:54:47 -0500 [thread overview]
Message-ID: <20141125235447.GE15033@fieldses.org> (raw)
Please pull the following nfsd bugfixes for 3.18:
git://linux-nfs.org/~bfields/linux.git for-3.18
These fix one mishandling of the case when security labels are
configured out, and two races in the 4.1 backchannel code.
--b.
----------------------------------------------------------------
Christoph Hellwig (1):
nfsd: correctly define v4.2 support attributes
Trond Myklebust (2):
SUNRPC: Fix locking around callback channel reply receive
nfsd: Fix slot wake up race in the nfsv4.1 callback code
fs/nfsd/nfs4callback.c | 8 ++++++--
fs/nfsd/nfsd.h | 9 ++++++---
net/sunrpc/svcsock.c | 27 ++++++++++++++++-----------
3 files changed, 28 insertions(+), 16 deletions(-)
next reply other threads:[~2014-11-25 23:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 23:54 J. Bruce Fields [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-27 21:51 [GIT PULL] nfsd bugfixes for 3.18 J. Bruce Fields
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=20141125235447.GE15033@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.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 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.