diff options
| author | Ronnie Sahlberg <[email protected]> | 2019-05-02 05:52:57 +0000 |
|---|---|---|
| committer | Steve French <[email protected]> | 2019-05-08 04:24:55 +0000 |
| commit | c425014afd7f622d586e7242f94019131790f5a3 (patch) | |
| tree | 98abb41afde40d638530693a9b0a591083a0b271 /drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c | |
| parent | cifs: zero-range does not require the file is sparse (diff) | |
| download | kernel-c425014afd7f622d586e7242f94019131790f5a3.tar.gz kernel-c425014afd7f622d586e7242f94019131790f5a3.zip | |
cifs: fix smb3_zero_range for Azure
For zero-range that also extend the file we were sending this as a
compound of two different operations; a fsctl to set-zero-data for the range
and then an additional set-info to extend the file size.
This does not work for Azure since it does not support this fsctl which leads
to fallocate(FALLOC_FL_ZERO_RANGE) failing but still changing the file size.
To fix this we un-compound this and send these two operations as separate
commands, firsat one command to set-zero-data for the range and it this
was successful we proceed to send a set-info to update the file size.
This fixes xfstest generic/469 for Azure servers.
Signed-off-by: Ronnie Sahlberg <[email protected]>
Signed-off-by: Steve French <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c')
0 files changed, 0 insertions, 0 deletions