forked from Minki/linux
fix incorrect error code mapping for OBJECTID_NOT_FOUND
It was mapped to EIO which can be confusing when user space queries for an object GUID for an object for which the server file system doesn't support (or hasn't saved one). As Amir Goldstein suggested this is similar to ENOATTR (equivalently ENODATA in Linux errno definitions) so changing NT STATUS code mapping for OBJECTID_NOT_FOUND to ENODATA. Signed-off-by: Steve French <stfrench@microsoft.com> CC: Amir Goldstein <amir73il@gmail.com>
This commit is contained in:
parent
b073a08016
commit
85f9987b23
@ -1036,7 +1036,8 @@ static const struct status_to_posix_error smb2_error_map_table[] = {
|
||||
{STATUS_UNFINISHED_CONTEXT_DELETED, -EIO,
|
||||
"STATUS_UNFINISHED_CONTEXT_DELETED"},
|
||||
{STATUS_NO_TGT_REPLY, -EIO, "STATUS_NO_TGT_REPLY"},
|
||||
{STATUS_OBJECTID_NOT_FOUND, -EIO, "STATUS_OBJECTID_NOT_FOUND"},
|
||||
/* Note that ENOATTTR and ENODATA are the same errno */
|
||||
{STATUS_OBJECTID_NOT_FOUND, -ENODATA, "STATUS_OBJECTID_NOT_FOUND"},
|
||||
{STATUS_NO_IP_ADDRESSES, -EIO, "STATUS_NO_IP_ADDRESSES"},
|
||||
{STATUS_WRONG_CREDENTIAL_HANDLE, -EIO,
|
||||
"STATUS_WRONG_CREDENTIAL_HANDLE"},
|
||||
|
Loading…
Reference in New Issue
Block a user