All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: andros@netapp.com
Cc: trondmy.myklebust@primarydata.com, anna.schumaker@netapp.com,
	linux-nfs@vger.kernel.org,
	Andy Adamson <andros@rhel7-2-ga-3.androsad.fake>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH Version-2 03/12] VFS permit cross device vfs_copy_file_range
Date: Fri, 19 Aug 2016 17:08:44 -0400	[thread overview]
Message-ID: <20160819210844.GR32329@fieldses.org> (raw)
In-Reply-To: <1471627512-4102-4-git-send-email-andros@netapp.com>

I thought I remembered Christoph (cc'd) arguing at the 2015 lsf/mm that
there were some more issues that would need to be taken care of before
we could turn on cross-device copies.

But maybe I misremember.  In any case, I don't remember what the issues
were....

--b.

On Fri, Aug 19, 2016 at 01:25:03PM -0400, andros@netapp.com wrote:
> From: Andy Adamson <andros@rhel7-2-ga-3.androsad.fake>
> 
> NFSv4.2 inter server to server copy always copies across devices.
> 
> Note: both btrfs and nfs have EXDEV checks in their
> copy_file_range functions.
> 
> Signed-off-by: Andy Adamson <andros@netapp.com>
> ---
>  fs/read_write.c | 5 -----
>  1 file changed, 5 deletions(-)
> 
> diff --git a/fs/read_write.c b/fs/read_write.c
> index 1cbab4e..a6d3350 100644
> --- a/fs/read_write.c
> +++ b/fs/read_write.c
> @@ -1483,7 +1483,6 @@ ssize_t vfs_copy_file_range(struct file *file_in, loff_t pos_in,
>  			    size_t len, unsigned int flags)
>  {
>  	struct inode *inode_in = file_inode(file_in);
> -	struct inode *inode_out = file_inode(file_out);
>  	ssize_t ret;
>  
>  	if (flags != 0)
> @@ -1505,10 +1504,6 @@ ssize_t vfs_copy_file_range(struct file *file_in, loff_t pos_in,
>  	    (file_out->f_flags & O_APPEND))
>  		return -EBADF;
>  
> -	/* this could be relaxed once a method supports cross-fs copies */
> -	if (inode_in->i_sb != inode_out->i_sb)
> -		return -EXDEV;
> -
>  	if (len == 0)
>  		return 0;
>  
> -- 
> 1.8.3.1

  reply	other threads:[~2016-08-19 21:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19 17:25 [PATCH Version-2 00/12] NFSv4.2 inter server to server copy andros
2016-08-19 17:25 ` [PATCH Version-2 01/12] fs: Don't copy beyond the end of the file andros
2016-08-20  6:19   ` Christoph Hellwig
2016-08-19 17:25 ` [PATCH Version-2 02/12] NFSD: Implement the COPY call andros
2016-08-19 17:25 ` [PATCH Version-2 03/12] VFS permit cross device vfs_copy_file_range andros
2016-08-19 21:08   ` J. Bruce Fields [this message]
2016-08-20  6:18     ` Christoph Hellwig
2016-08-22 19:27       ` J. Bruce Fields
2016-08-24 18:38       ` Adamson, Andy
2016-08-24 18:38         ` Adamson, Andy
2016-08-19 17:25 ` [PATCH Version-2 04/12] NFS inter ssc open andros
2016-08-19 21:11   ` J. Bruce Fields
2016-08-19 17:25 ` [PATCH Version-2 05/12] NFS add COPY_NOTIFY operation andros
2016-08-19 17:25 ` [PATCH Version-2 06/12] NFS add ca_source_server<> to COPY andros
2016-08-19 17:25 ` [PATCH Version-2 07/12] NFSD " andros
2016-08-19 17:25 ` [PATCH Version-2 08/12] NFSD add COPY_NOTIFY operation andros
2016-08-19 17:25 ` [PATCH Version-2 09/12] NFSD generalize nfsd4_compound_state flag names andros
2016-08-19 17:25 ` [PATCH Version-2 10/12] NFSD: allow inter server COPY to have a STALE source server fh andros
2016-08-19 17:25 ` [PATCH Version-2 11/12] NFSD add nfs4 inter ssc to nfsd4_copy andros
2016-08-19 17:25 ` [PATCH Version-2 12/12] NFSD: extra stateid checking in read for interserver copy andros
2016-08-19 21:26 ` [PATCH Version-2 00/12] NFSv4.2 inter server to server copy 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=20160819210844.GR32329@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=andros@netapp.com \
    --cc=andros@rhel7-2-ga-3.androsad.fake \
    --cc=anna.schumaker@netapp.com \
    --cc=hch@lst.de \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trondmy.myklebust@primarydata.com \
    /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.