fix incorrect error code mapping for OBJECTID_NOT_FOUND
authorSteve French <stfrench@microsoft.com>
Sun, 17 Mar 2019 20:58:38 +0000 (15:58 -0500)
committerSteve French <stfrench@microsoft.com>
Sat, 23 Mar 2019 03:36:54 +0000 (22:36 -0500)
commit85f9987b236cf46e06ffdb5c225cf1f3c0acb789
tree5e82b821d8acadebf39de27d494012759232953d
parentb073a08016a10f01dfb0d0b6c7fa89da0d544963
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>
fs/cifs/smb2maperror.c