From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs.git, part 4 - copy_file_range stuff
Date: Tue, 12 Jan 2016 03:27:21 +0000 [thread overview]
Message-ID: <20160112032721.GQ17997@ZenIV.linux.org.uk> (raw)
Several series around copy_file_range/CLONE. Please, pull from
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.copy_file_range
Shortlog:
Anna Schumaker (2):
vfs: Add vfs_copy_file_range() support for pagecache copies
nfsd: Pass filehandle to nfs4_preprocess_stateid_op()
Arnd Bergmann (1):
cifs: avoid unused variable and label
Christoph Hellwig (3):
locks: new locks_mandatory_area calling convention
vfs: pull btrfs clone API to vfs layer
nfsd: implement the NFSv4.2 CLONE operation
Darrick J. Wong (3):
vfs: wire up compat ioctl for CLONE/CLONE_RANGE
vfs: hoist the btrfs deduplication ioctl to the vfs
btrfs: use new dedupe data function pointer
Zach Brown (3):
vfs: add copy_file_range syscall and vfs helper
x86: add sys_copy_file_range to syscall tables
btrfs: add .copy_file_range file operation
Diffstat:
arch/x86/entry/syscalls/syscall_32.tbl | 1 +
arch/x86/entry/syscalls/syscall_64.tbl | 1 +
fs/btrfs/ctree.h | 8 +-
fs/btrfs/file.c | 3 +
fs/btrfs/ioctl.c | 186 ++++----------------
fs/cifs/cifsfs.c | 61 +++++++
fs/cifs/cifsfs.h | 1 -
fs/cifs/ioctl.c | 126 +++++++-------
fs/compat_ioctl.c | 5 +
fs/ioctl.c | 67 ++++++++
fs/locks.c | 22 +--
fs/nfs/nfs4file.c | 87 ++--------
fs/nfsd/nfs4proc.c | 63 ++++++-
fs/nfsd/nfs4state.c | 5 +-
fs/nfsd/nfs4xdr.c | 21 +++
fs/nfsd/state.h | 4 +-
fs/nfsd/vfs.c | 8 +
fs/nfsd/vfs.h | 2 +
fs/nfsd/xdr4.h | 10 ++
fs/read_write.c | 302 ++++++++++++++++++++++++++++++++-
include/linux/fs.h | 42 +++--
include/linux/nfs4.h | 4 +-
include/linux/syscalls.h | 3 +
include/uapi/asm-generic/unistd.h | 4 +-
include/uapi/linux/fs.h | 39 +++++
kernel/sys_ni.c | 1 +
26 files changed, 733 insertions(+), 343 deletions(-)
reply other threads:[~2016-01-12 3:27 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=20160112032721.GQ17997@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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.