diff options
author | Ronnie Sahlberg | 2022-04-21 11:15:36 +1000 |
---|---|---|
committer | Steve French | 2022-04-20 22:54:54 -0500 |
commit | f5d0f921ea362636e4a2efb7c38d1ead373a8700 (patch) | |
tree | 00c6b71fb425817a6afb3e2e355b22387da2aefd /mm | |
parent | cd70a3e8988a999c42d307d2616a5e7b6a33c7c8 (diff) |
cifs: destage any unwritten data to the server before calling copychunk_write
because the copychunk_write might cover a region of the file that has not yet
been sent to the server and thus fail.
A simple way to reproduce this is:
truncate -s 0 /mnt/testfile; strace -f -o x -ttT xfs_io -i -f -c 'pwrite 0k 128k' -c 'fcollapse 16k 24k' /mnt/testfile
the issue is that the 'pwrite 0k 128k' becomes rearranged on the wire with
the 'fcollapse 16k 24k' due to write-back caching.
fcollapse is implemented in cifs.ko as a SMB2 IOCTL(COPYCHUNK_WRITE) call
and it will fail serverside since the file is still 0b in size serverside
until the writes have been destaged.
To avoid this we must ensure that we destage any unwritten data to the
server before calling COPYCHUNK_WRITE.
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1997373
Reported-by: Xiaoli Feng <xifeng@redhat.com>
Signed-off-by: Ronnie Sahlberg <lsahlber@redhat.com>
Signed-off-by: Steve French <stfrench@microsoft.com>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions