From: Peng Tao <tao.peng@primarydata.com>
To: linux-fsdevel@vger.kernel.org
Cc: Trond Myklebust <trond.myklebust@primarydata.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
Christoph Hellwig <hch@infradead.org>, Zach Brown <zab@zabbo.net>,
Darren Hart <dvhart@linux.intel.com>,
Jeff Layton <jeff.layton@primarydata.com>,
bfields@fieldses.org, "Darrick J. Wong" <darrick.wong@oracle.com>,
viro@zeniv.linux.org.uk, linux-nfs@vger.kernel.org,
linux-btrfs@vger.kernel.org, linux-cifs@vger.kernel.org,
Steve French <steve.french@primarydata.com>,
Peng Tao <tao.peng@primarydata.com>
Subject: [PATCH 0/9] vfs: move btrfs clone ioctls to common code
Date: Sun, 25 Oct 2015 07:17:07 +0800 [thread overview]
Message-ID: <1445728636-10109-1-git-send-email-tao.peng@primarydata.com> (raw)
Hi all,
This patchset moves BTRFS_IOC_CLONE/BTRFS_IOC_CLONE_RANGE to common vfs
layer and adds NFS42 CLONE support to knfsd.
It is based on top of Trond's linux-next branch (a85240d254) and Anna's latest
sys_copy_file_range work (v7).
With this, btrfs/cifs/nfs all handle CLONE/CLONE_RANGE ioctls through the
.copy_file_range method instead of each implementing them in the private
ioctl handlers.
Cheers,
Tao
Anna Schumaker (2):
nfsd: Pass filehandle to nfs4_preprocess_stateid_op()
NFSD: Implement the CLONE call
Peng Tao (7):
vfs: add COPY_FILE_CLONE_ONLY flag
cifs: add .copy_file_range file operation
nfs42: add .copy_file_range file operation
vfs: pull btrfs clone API to vfs layer
btrfs: remove btrfs_ioctl_clone(_range)
cifs: remove private handler of BTRFS_IOC_CLONE
nfs42: remove private clone ioctl handler
fs/btrfs/ioctl.c | 49 ------------------
fs/cifs/cifsfs.c | 22 ++++++++
fs/cifs/cifsfs.h | 4 +-
fs/cifs/ioctl.c | 103 ++++++++++++++++++++-----------------
fs/ioctl.c | 40 +++++++++++++++
fs/nfs/nfs4file.c | 133 +++++++++---------------------------------------
fs/nfsd/nfs4proc.c | 96 +++++++++++++++++++++++++++++++---
fs/nfsd/nfs4state.c | 6 +--
fs/nfsd/nfs4xdr.c | 21 ++++++++
fs/nfsd/state.h | 5 +-
fs/nfsd/vfs.c | 12 +++++
fs/nfsd/vfs.h | 1 +
fs/nfsd/xdr4.h | 10 ++++
fs/read_write.c | 9 ++--
include/linux/fs.h | 3 ++
include/linux/nfs4.h | 4 +-
include/uapi/linux/fs.h | 9 ++++
17 files changed, 303 insertions(+), 224 deletions(-)
--
1.8.3.1
next reply other threads:[~2015-10-24 15:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-24 23:17 Peng Tao [this message]
2015-10-24 23:17 ` [PATCH 1/9] vfs: add COPY_FILE_CLONE_ONLY flag Peng Tao
2015-11-13 8:58 ` Christoph Hellwig
2015-10-24 23:17 ` [PATCH 2/9] cifs: add .copy_file_range file operation Peng Tao
2015-10-27 17:13 ` Steve French
2015-10-24 23:17 ` [PATCH 3/9] nfs42: " Peng Tao
2015-10-24 23:17 ` [PATCH 4/9] vfs: pull btrfs clone API to vfs layer Peng Tao
2015-10-24 23:17 ` [PATCH 5/9] btrfs: remove btrfs_ioctl_clone(_range) Peng Tao
2015-10-24 23:17 ` [PATCH 6/9] cifs: remove private handler of BTRFS_IOC_CLONE Peng Tao
2015-10-24 23:17 ` [PATCH 7/9] nfs42: remove private clone ioctl handler Peng Tao
2015-10-24 23:17 ` [PATCH 8/9] nfsd: Pass filehandle to nfs4_preprocess_stateid_op() Peng Tao
2015-10-24 23:17 ` [PATCH 9/9] NFSD: Implement the CLONE call Peng Tao
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=1445728636-10109-1-git-send-email-tao.peng@primarydata.com \
--to=tao.peng@primarydata.com \
--cc=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=darrick.wong@oracle.com \
--cc=dvhart@linux.intel.com \
--cc=hch@infradead.org \
--cc=jeff.layton@primarydata.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=steve.french@primarydata.com \
--cc=trond.myklebust@primarydata.com \
--cc=viro@zeniv.linux.org.uk \
--cc=zab@zabbo.net \
/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).