From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yb1-f194.google.com ([209.85.219.194]:42386 "EHLO mail-yb1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726238AbeLCM4y (ORCPT ); Mon, 3 Dec 2018 07:56:54 -0500 MIME-Version: 1.0 References: <20181203083416.28978-1-david@fromorbit.com> <20181203083416.28978-12-david@fromorbit.com> In-Reply-To: <20181203083416.28978-12-david@fromorbit.com> From: Amir Goldstein Date: Mon, 3 Dec 2018 14:55:46 +0200 Message-ID: Subject: Re: [PATCH 11/11] ovl: allow cross-device copy_file_range calls Content-Type: text/plain; charset="UTF-8" Sender: linux-unionfs-owner@vger.kernel.org To: Dave Chinner Cc: linux-fsdevel , linux-xfs , Olga Kornievskaia , Linux NFS Mailing List , overlayfs , ceph-devel@vger.kernel.org, linux-cifs@vger.kernel.org List-ID: On Mon, Dec 3, 2018 at 10:34 AM Dave Chinner wrote: > > From: Dave Chinner > > Restrictions on cross-device copy_file_range() only affect the > vfs_copy_file_range() call to the lower filesystems. They will > handle the copy appropriately, so OVL will never see a EXDEV error > from them. Hence we can remove the EXDEV checks and error handling > from the ovl_copy_file_range() implementation. > > Signed-off-by: Dave Chinner > --- Looks good. Reviewed-by: Amir Goldstein Thanks, Amir.