From: <Anna.Schumaker@netapp.com>
To: <bfields@fieldses.org>
Cc: <linux-nfs@vger.kernel.org>
Subject: [PATCH v2 0/2] NFSD: Add ALLOCATE and DEALLOCATE support
Date: Fri, 24 Oct 2014 10:41:43 -0400 [thread overview]
Message-ID: <1414161705-26617-1-git-send-email-Anna.Schumaker@Netapp.com> (raw)
From: Anna Schumaker <Anna.Schumaker@Netapp.com>
These patches add server support for the ALLOCATE and DEALLOCATE operations
part of NFS v4.2.
I submitted my do_fallocate() -> vfs_fallocate() change as a separate patch,
so it has been removed from this submission. However, this code still depends
on this patch being applied first.
Changes in v2:
- ALLOCATE and DEALLOCATE can call a common nfsd4_fallocate() to check the
stateids, look up the file, and eventually call nfsd4_vfs_fallocate().
- I return NFS4ERR_INVAL in the case that vfs_fallocate() returns -ENODEV.
Please let me know if there is a better error to return instead!
These patches and the corresponding client changes are available in the
[fallocate] branch of:
git://git.linux-nfs.org/projects/anna/linux-nfs.git
Questions? Comments? Thoughts?
Anna
Anna Schumaker (2):
nfsd: Add ALLOCATE support
nfsd: Add DEALLOCATE support
fs/nfsd/nfs4proc.c | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++
fs/nfsd/nfs4xdr.c | 21 +++++++++++++++++++--
fs/nfsd/vfs.c | 19 +++++++++++++++++++
fs/nfsd/vfs.h | 2 ++
fs/nfsd/xdr4.h | 9 +++++++++
5 files changed, 100 insertions(+), 2 deletions(-)
--
2.1.2
next reply other threads:[~2014-10-24 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 14:41 Anna.Schumaker [this message]
2014-10-24 14:41 ` [PATCH v2 1/2] nfsd: Add ALLOCATE support Anna.Schumaker
2014-10-28 8:41 ` Christoph Hellwig
2014-10-28 19:09 ` Anna Schumaker
2014-10-24 14:41 ` [PATCH v2 2/2] nfsd: Add DEALLOCATE support Anna.Schumaker
2014-10-28 8:37 ` [PATCH v2 0/2] NFSD: Add ALLOCATE and " Christoph Hellwig
2014-10-28 20:48 ` 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=1414161705-26617-1-git-send-email-Anna.Schumaker@Netapp.com \
--to=anna.schumaker@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