diff options
| author | Steve French <stfrench@microsoft.com> | 2021-11-10 10:47:48 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2021-12-01 11:19:08 +0300 |
| commit | 5655b8bccb8a19a34c83225a1c7bf2adca50c2c3 (patch) | |
| tree | 800c4d2b24bae03a0e8e92b992c2c060f0eb54cb /drivers/iommu/amd | |
| parent | c380062d0850d854578ef47ca714f135e6597a99 (diff) | |
| download | linux-5655b8bccb8a19a34c83225a1c7bf2adca50c2c3.tar.xz | |
smb3: do not error on fsync when readonly
[ Upstream commit 71e6864eacbef0b2645ca043cdfbac272cb6cea3 ]
Linux allows doing a flush/fsync on a file open for read-only,
but the protocol does not allow that. If the file passed in
on the flush is read-only try to find a writeable handle for
the same inode, if that is not possible skip sending the
fsync call to the server to avoid breaking the apps.
Reported-by: Julian Sikorski <belegdol@gmail.com>
Tested-by: Julian Sikorski <belegdol@gmail.com>
Suggested-by: Jeremy Allison <jra@samba.org>
Reviewed-by: Paulo Alcantara (SUSE) <pc@cjr.nz>
Signed-off-by: Steve French <stfrench@microsoft.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/iommu/amd')
0 files changed, 0 insertions, 0 deletions