From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from verein.lst.de ([213.95.11.211]:56966 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750841AbdCBQjz (ORCPT ); Thu, 2 Mar 2017 11:39:55 -0500 Date: Thu, 2 Mar 2017 17:07:14 +0100 From: Christoph Hellwig To: Olga Kornievskaia Cc: linux-fsdevel@vger.kernel.org, hch@lst.de, linux-nfs@vger.kernel.org Subject: Re: [PATCH v1 2/3] VFS permit cross device vfs_copy_file_range Message-ID: <20170302160714.GA4760@lst.de> References: <20170302160211.30451-1-kolga@netapp.com> <20170302160211.30451-3-kolga@netapp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170302160211.30451-3-kolga@netapp.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Mar 02, 2017 at 11:02:10AM -0500, Olga Kornievskaia wrote: > Allow nfs_copy_file_range to copy across devices. > NFSv4.2 inter server to server copy always copies across devices, and > NFSv4.2 intra server to server copy can copy across devices on the same > server. > > If a file system's fileoperations copy_file_range operation prohibits > cross-device copies, fall back to do_splice_direct. This is needed for > nfsd_copy_file_range() which is called by the inter server to server > destination server acting as an NFS client, and reading the file from > the source server. NAK, we really should not do operations between different superblocks.