From: Yu Xu <xuyu@linux.alibaba.com>
To: gregkh@linuxfoundation.org, kolga@netapp.com, linux-nfs@vger.kernel.org
Cc: joseph.qi@linux.alibaba.com, caspar@linux.alibaba.com
Subject: [backport request][stable] NFSv4.x: fix incorrect return value in copy_file_range
Date: Thu, 23 May 2019 23:59:30 +0800 [thread overview]
Message-ID: <0f0e59bd-2520-e265-265e-4a29bf776c60@linux.alibaba.com> (raw)
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?
Thanks,
Yu
next reply other threads:[~2019-05-23 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 15:59 Yu Xu [this message]
2019-05-27 14:09 ` [backport request][stable] NFSv4.x: fix incorrect return value in copy_file_range Greg KH
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=0f0e59bd-2520-e265-265e-4a29bf776c60@linux.alibaba.com \
--to=xuyu@linux.alibaba.com \
--cc=caspar@linux.alibaba.com \
--cc=gregkh@linuxfoundation.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=kolga@netapp.com \
--cc=linux-nfs@vger.kernel.org \
/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