From: Anna Schumaker <Anna.Schumaker@netapp.com>
To: linux-nfs@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org,
zab@zabbo.net, viro@zeniv.linux.org.uk, clm@fb.com,
darrick.wong@oracle.com, mtk.manpages@gmail.com,
andros@netapp.com, hch@infradead.org
Subject: [PATCH v4 9/9] btrfs: btrfs_copy_file_range() only supports reflinks
Date: Tue, 29 Sep 2015 14:05:12 -0400 [thread overview]
Message-ID: <1443549913-8091-10-git-send-email-Anna.Schumaker@Netapp.com> (raw)
In-Reply-To: <1443549913-8091-1-git-send-email-Anna.Schumaker@Netapp.com>
Reject copies that don't have the COPY_FR_REFLINK flag set.
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Reviewed-by: David Sterba <dsterba@suse.com>
---
fs/btrfs/ioctl.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
index 4311554..2e14b91 100644
--- a/fs/btrfs/ioctl.c
+++ b/fs/btrfs/ioctl.c
@@ -44,6 +44,7 @@
#include <linux/uuid.h>
#include <linux/btrfs.h>
#include <linux/uaccess.h>
+#include <linux/copy.h>
#include "ctree.h"
#include "disk-io.h"
#include "transaction.h"
@@ -3848,6 +3849,9 @@ ssize_t btrfs_copy_file_range(struct file *file_in, loff_t pos_in,
{
ssize_t ret;
+ if (!(flags & COPY_FR_REFLINK))
+ return -EOPNOTSUPP;
+
ret = btrfs_clone_files(file_out, file_in, pos_in, len, pos_out);
if (ret == 0)
ret = len;
--
2.5.3
next prev parent reply other threads:[~2015-09-29 18:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 18:05 [PATCH v4 0/9] VFS: In-kernel copy system call Anna Schumaker
2015-09-29 18:05 ` [PATCH v4 1/9] vfs: add copy_file_range syscall and vfs helper Anna Schumaker
[not found] ` <1443549913-8091-1-git-send-email-Anna.Schumaker-ZwjVKphTwtPQT0dZR+AlfA@public.gmane.org>
2015-09-29 18:05 ` [PATCH v4 2/9] x86: add sys_copy_file_range to syscall tables Anna Schumaker
2015-09-29 18:05 ` [PATCH v4 3/9] btrfs: add .copy_file_range file operation Anna Schumaker
[not found] ` <1443549913-8091-4-git-send-email-Anna.Schumaker-ZwjVKphTwtPQT0dZR+AlfA@public.gmane.org>
2015-09-30 3:20 ` Zhao Lei
2015-09-30 12:55 ` Anna Schumaker
2015-09-29 18:05 ` [PATCH v4 5/9] vfs: Copy shouldn't forbid ranges inside the same file Anna Schumaker
2015-09-29 18:05 ` [PATCH v4 6/9] vfs: Copy should use file_out rather than file_in Anna Schumaker
2015-09-29 18:05 ` [PATCH v4 7/9] vfs: Remove copy_file_range mountpoint checks Anna Schumaker
2015-09-29 18:05 ` [PATCH v4 8/9] vfs: Add vfs_copy_file_range() support for pagecache copies Anna Schumaker
2015-09-29 18:05 ` [PATCH v4 4/9] vfs: Copy should check len after file open mode Anna Schumaker
2015-09-29 18:05 ` Anna Schumaker [this message]
2015-09-29 18:05 ` [PATCH v4 10/9] copy_file_range.2: New page documenting copy_file_range() Anna Schumaker
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=1443549913-8091-10-git-send-email-Anna.Schumaker@Netapp.com \
--to=anna.schumaker@netapp.com \
--cc=andros@netapp.com \
--cc=clm@fb.com \
--cc=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mtk.manpages@gmail.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).