From: Chuck Lever III <chuck.lever@oracle.com>
To: Dai Ngo <dai.ngo@oracle.com>
Cc: Olga Kornievskaia <aglo@umich.edu>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Brian Foster <bfoster@redhat.com>
Subject: Re: [PATCH] NFSD: pass range end to vfs_fsync_range() instead of count
Date: Wed, 16 Nov 2022 19:01:16 +0000 [thread overview]
Message-ID: <F8A4FD38-41F4-4B03-99D9-7043CD3977FF@oracle.com> (raw)
In-Reply-To: <5163ae19-b78b-d047-f700-93b3ad651eea@oracle.com>
> On Nov 16, 2022, at 1:50 PM, Dai Ngo <dai.ngo@oracle.com> wrote:
>
>
> On 11/16/22 7:34 AM, Chuck Lever III wrote:
>>
>>> On Nov 16, 2022, at 10:28 AM, Brian Foster <bfoster@redhat.com> wrote:
>>>
>>> _nfsd_copy_file_range() calls vfs_fsync_range() with an offset and
>>> count (bytes written), but the former wants the start and end bytes
>>> of the range to sync. Fix it up.
>>>
>>> Fixes: eac0b17a77fb ("NFSD add vfs_fsync after async copy is done")
>>> Signed-off-by: Brian Foster <bfoster@redhat.com>
>>> ---
>>>
>>> Hi all,
>>>
>>> This is just a quick drive-by patch from scanning through various flush
>>> callers for something unrelated. It looked like this instance passes a
>>> count instead of the end offset and it was easy enough to throw up a
>>> patch. Compile tested only, feel free to toss it if I've just missed
>>> something, etc. etc.
>> Dai, Olga, can you review this, and one of you test it?
>
> LGTM, tested ok.
May I add Tested-by: Dai Ngo <dai.ngo@oracle.com> ?
> -Dai
>
>>
>>
>>> Brian
>>>
>>> fs/nfsd/nfs4proc.c | 5 +++--
>>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/fs/nfsd/nfs4proc.c b/fs/nfsd/nfs4proc.c
>>> index 8beb2bc4c328..3c67d4cb1eba 100644
>>> --- a/fs/nfsd/nfs4proc.c
>>> +++ b/fs/nfsd/nfs4proc.c
>>> @@ -1644,6 +1644,7 @@ static ssize_t _nfsd_copy_file_range(struct nfsd4_copy *copy,
>>> u64 src_pos = copy->cp_src_pos;
>>> u64 dst_pos = copy->cp_dst_pos;
>>> int status;
>>> + loff_t end;
>>>
>>> /* See RFC 7862 p.67: */
>>> if (bytes_total == 0)
>>> @@ -1663,8 +1664,8 @@ static ssize_t _nfsd_copy_file_range(struct nfsd4_copy *copy,
>>> /* for a non-zero asynchronous copy do a commit of data */
>>> if (nfsd4_copy_is_async(copy) && copy->cp_res.wr_bytes_written > 0) {
>>> since = READ_ONCE(dst->f_wb_err);
>>> - status = vfs_fsync_range(dst, copy->cp_dst_pos,
>>> - copy->cp_res.wr_bytes_written, 0);
>>> + end = copy->cp_dst_pos + copy->cp_res.wr_bytes_written - 1;
>>> + status = vfs_fsync_range(dst, copy->cp_dst_pos, end, 0);
>>> if (!status)
>>> status = filemap_check_wb_err(dst->f_mapping, since);
>>> if (!status)
>>> --
>>> 2.37.3
>>>
>> --
>> Chuck Lever
--
Chuck Lever
next prev parent reply other threads:[~2022-11-16 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 15:28 [PATCH] NFSD: pass range end to vfs_fsync_range() instead of count Brian Foster
2022-11-16 15:34 ` Chuck Lever III
2022-11-16 18:50 ` dai.ngo
2022-11-16 19:01 ` Chuck Lever III [this message]
2022-11-16 19:08 ` dai.ngo
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=F8A4FD38-41F4-4B03-99D9-7043CD3977FF@oracle.com \
--to=chuck.lever@oracle.com \
--cc=aglo@umich.edu \
--cc=bfoster@redhat.com \
--cc=dai.ngo@oracle.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