diff options
| author | Andy Ryan <genanr@allantgroup.com> | 2006-11-07 14:36:26 -0600 |
|---|---|---|
| committer | Trond Myklebust <Trond.Myklebust@netapp.com> | 2006-12-06 10:46:26 -0500 |
| commit | 46b9f8e1484352f09f229107ba2a758fe386d7f7 (patch) | |
| tree | 544f971bf1034fa34c0d9b5cf2f5aeaabc3d413b | |
| parent | 8aca67f0ae2d8811165c22326825a645cc8e1b48 (diff) | |
| download | op-kernel-dev-46b9f8e1484352f09f229107ba2a758fe386d7f7.zip op-kernel-dev-46b9f8e1484352f09f229107ba2a758fe386d7f7.tar.gz | |
NFS Exclusive open not supported bug
When trying to open a file with the O_EXCL flag over NFS on a server that does
not support exclusive mode, the file does not open. The reason,
rpc_call_sync returns a errno number, and not the nfs error number. I fixed
it by changing the status check in nfs3proc.c. Either this is how it should
be fixed, or rpc_call_sync should be fixed to return the NFS error.
Signed-off-by: Andy Ryan <genanr@allantgroup.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
| -rw-r--r-- | fs/nfs/nfs3proc.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/nfs/nfs3proc.c b/fs/nfs/nfs3proc.c index e5f128f..9d7ff4f 100644 --- a/fs/nfs/nfs3proc.c +++ b/fs/nfs/nfs3proc.c @@ -369,7 +369,7 @@ again: /* If the server doesn't support the exclusive creation semantics, * try again with simple 'guarded' mode. */ - if (status == NFSERR_NOTSUPP) { + if (status == -ENOTSUPP) { switch (arg.createmode) { case NFS3_CREATE_EXCLUSIVE: arg.createmode = NFS3_CREATE_GUARDED; |
