From: <bjschuma@netapp.com>
To: <bfields@fieldses.org>
Cc: <linux-nfs@vger.kernel.org>
Subject: [PATCH 0/3] NFSD: Add v4.2 SEEK support
Date: Wed, 27 Aug 2014 11:17:55 -0400 [thread overview]
Message-ID: <1409152678-7806-1-git-send-email-bjschuma@netapp.com> (raw)
From: Anna Schumaker <Anna.Schumaker@Netapp.com>
These patches add server support for the NFS v4.2 operation SEEK. The first
two patches are error cleanups and infrastructure setup to prepare for the
addition of new operations.
My biggest concern is that these patches freeze the v4.2 opcodes to their
current values, which makes any future spec changes to add or remove
operations more difficult to accomidate.
Questions? Comments? Thoughts?
Anna
Anna Schumaker (3):
NFSD: Update error codes
NFSD: Create nfs v4.2 decode ops
NFSD: Implement SEEK
fs/nfsd/Kconfig | 12 +++++++++
fs/nfsd/nfs4proc.c | 47 +++++++++++++++++++++++++++++++++
fs/nfsd/nfs4xdr.c | 73 ++++++++++++++++++++++++++++++++++++++++++++++++++++
fs/nfsd/nfsd.h | 2 +-
fs/nfsd/xdr4.h | 14 ++++++++++
include/linux/nfs4.h | 26 ++++++++++++++++---
6 files changed, 170 insertions(+), 4 deletions(-)
--
2.1.0
next reply other threads:[~2014-08-27 15:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 15:17 bjschuma [this message]
2014-08-27 15:17 ` [PATCH 1/3] NFSD: Update error codes bjschuma
2014-08-27 17:59 ` J. Bruce Fields
2014-08-27 15:17 ` [PATCH 2/3] NFSD: Create nfs v4.2 decode ops bjschuma
2014-08-27 17:42 ` Christoph Hellwig
2014-08-27 18:04 ` J. Bruce Fields
2014-08-27 15:17 ` [PATCH 3/3] NFSD: Implement SEEK bjschuma
2014-08-27 19:09 ` J. Bruce Fields
2014-08-27 19:21 ` Anna Schumaker
2014-08-27 19:29 ` J. Bruce Fields
2014-08-27 19:35 ` J. Bruce Fields
2014-08-27 19:39 ` [PATCH 0/3] NFSD: Add v4.2 SEEK support 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=1409152678-7806-1-git-send-email-bjschuma@netapp.com \
--to=bjschuma@netapp.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@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