summaryrefslogtreecommitdiff
path: root/fs
diff options
context:
space:
mode:
authorFrank Filz <ffilzlnx@us.ibm.com>2009-05-18 17:41:40 -0400
committerGreg Kroah-Hartman <gregkh@suse.de>2009-06-11 20:01:06 -0700
commit218cadbd4ce2a81d417b6f7b5eb5d5460f221fec (patch)
tree0e79537013302172954b9275796ab9ce9d9cf259 /fs
parent7357e333ed90064893f5e09c6b2763c2faaf51dd (diff)
nfs: Fix NFS v4 client handling of MAY_EXEC in nfs_permission.
commit 7ee2cb7f32b299c2b06a31fde155457203e4b7dd upstream. The problem is that permission checking is skipped if atomic open is possible, but when exec opens a file, it just opens it O_READONLY which means EXEC permission will not be checked at that time. This problem is observed by the following sequence (executed as root): mount -t nfs4 server:/ /mnt4 echo "ls" >/mnt4/foo chmod 744 /mnt4/foo su guest -c "mnt4/foo" Signed-off-by: Frank Filz <ffilzlnx@us.ibm.com> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com> Tested-by: Eugene Teo <eugeneteo@kernel.sg> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'fs')
-rw-r--r--fs/nfs/dir.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/fs/nfs/dir.c b/fs/nfs/dir.c
index bff873311b40..c3fe156dc462 100644
--- a/fs/nfs/dir.c
+++ b/fs/nfs/dir.c
@@ -1925,7 +1925,8 @@ int nfs_permission(struct inode *inode, int mask)
case S_IFREG:
/* NFSv4 has atomic_open... */
if (nfs_server_capable(inode, NFS_CAP_ATOMIC_OPEN)
- && (mask & MAY_OPEN))
+ && (mask & MAY_OPEN)
+ && !(mask & MAY_EXEC))
goto out;
break;
case S_IFDIR: