Received-SPF: pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Mon, 27 May 2019 16:09:21 +0200
From:   Greg KH <gregkh@linuxfoundation.org>
To:     Yu Xu <xuyu@linux.alibaba.com>
Cc:     kolga@netapp.com, linux-nfs@vger.kernel.org,
        joseph.qi@linux.alibaba.com, caspar@linux.alibaba.com
Subject: Re: [backport request][stable] NFSv4.x: fix incorrect return value
 in copy_file_range
Message-ID: <20190527140921.GD7659@kroah.com>
References: <0f0e59bd-2520-e265-265e-4a29bf776c60@linux.alibaba.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0f0e59bd-2520-e265-265e-4a29bf776c60@linux.alibaba.com>
User-Agent: Mutt/1.12.0 (2019-05-25)
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk

On Thu, May 23, 2019 at 11:59:30PM +0800, Yu Xu wrote:
> Hi,
> 
> I'm using kernel v4.19.y and find that v4.19.y fails in the latest xfstests
> generic/075, 091, 112, 127 and 263, which can be simply reproduced as
> follows:
> 
> # kernel 4.19.y
> $ xfs_io -fc "copy_range -s 0 -d 1 -l 1 /mnt/nfs/file" /mnt/nfs/file
> copy_range: Invalid argument
> 
> # kernel 5.1.0
> $ xfs_io -fc "copy_range -s 0 -d 1 -l 1 /mnt/nfs/file" /mnt/nfs/file
> # success
> 
> I notice that upstream (v5.1+) has already fixed this issue with:
> 1) commit 45ac486ecf2dc998e25cf32f0cabf2deaad875be
> 2) commit 0769663b4f580566ef6cdf366f3073dbe8022c39
> 
> But these patches do not cc stable@vger.kernel.org (why? forgotten?). And
> will v4.19.y consider to backport these patches?

I will be glad to queue them up now, thanks for letting me know.

greg k-h