diff options
author | Jeff Layton <jlayton@redhat.com> | 2012-09-24 15:33:40 +0200 |
---|---|---|
committer | Steve French <smfrench@gmail.com> | 2012-09-26 19:55:42 +0200 |
commit | 4f2b86aba87a2654a1258ffe09c22ce70ab69d60 (patch) | |
tree | fee73aa6f710fb3d09fd7131d092024c49d3c361 /fs/cifs/smb1ops.c | |
parent | cifs: remove support for deprecated "forcedirectio" and "strictcache" mount o... (diff) | |
download | linux-4f2b86aba87a2654a1258ffe09c22ce70ab69d60.tar.xz linux-4f2b86aba87a2654a1258ffe09c22ce70ab69d60.zip |
cifs: change DOS/NT/POSIX mapping of ERRnoresource
ERRnoresource is an ERRSRV level (aka server-side) error and means "No
resources currently available for request". Currently that maps to POSIX
-ENOBUFS. No NT errors map to it currently.
NT_STATUS_INSUFFICIENT_RESOURCES and NT_STATUS_INSUFF_SERVER_RESOURCES
are also similar in meaning. Currently the client maps those to
ERRnomem, which maps to -ENOMEM in POSIX.
All of these mappings seem to be quite wrong to me and are confusing for
users. All of the above errors indicate problems on the server, not the
client. Reporting -ENOMEM or -ENOBUFS implies that the client is running
out of resources.
This patch changes those mappings. The NT_* errors are changed to map to
the SRV level ERRnoresource. That error is in turn changed to return
-EREMOTEIO which is the only POSIX error I could find that conveys that
something went wrong on the server. While we're at it, change the SMB2
equivalent error to return the same.
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Acked-by: Suresh Jayaraman <sjayaraman@suse.com>
Signed-off-by: Steve French <smfrench@gmail.com>
Diffstat (limited to 'fs/cifs/smb1ops.c')
0 files changed, 0 insertions, 0 deletions