diff options
| author | Steve French <stfrench@microsoft.com> | 2019-09-11 00:07:36 -0500 |
|---|---|---|
| committer | Steve French <stfrench@microsoft.com> | 2019-09-16 11:43:38 -0500 |
| commit | 7dcc82c2dfd5f12eba19d19d39c50bff70b4f94a (patch) | |
| tree | 747ebf69fae8d2004d3d601039058d6dfbb0080e /fs/d_path.c | |
| parent | 1b63f1840e787516bf2d3e5c27c2d22fe23cfb37 (diff) | |
| download | linux-7dcc82c2dfd5f12eba19d19d39c50bff70b4f94a.tar.bz2 | |
smb3: improve handling of share deleted (and share recreated)
When a share is deleted, returning EIO is confusing and no useful
information is logged. Improve the handling of this case by
at least logging a better error for this (and also mapping the error
differently to EREMCHG). See e.g. the new messages that would be logged:
[55243.639530] server share \\192.168.1.219\scratch deleted
[55243.642568] CIFS VFS: \\192.168.1.219\scratch BAD_NETWORK_NAME: \\192.168.1.219\scratch
In addition for the case where a share is deleted and then recreated
with the same name, have now fixed that so it works. This is sometimes
done for example, because the admin had to move a share to a different,
bigger local drive when a share is running low on space.
Signed-off-by: Steve French <stfrench@microsoft.com>
Reviewed-by: Ronnie Sahlberg <lsahlber@redhat.com>
Diffstat (limited to 'fs/d_path.c')
0 files changed, 0 insertions, 0 deletions