summaryrefslogtreecommitdiff
path: root/fs/cifs/CHANGES
diff options
context:
space:
mode:
authorSteve French <sfrench@us.ibm.com>2008-12-05 19:14:12 +0000
committerSteve French <sfrench@us.ibm.com>2008-12-26 02:29:11 +0000
commit8be0ed44c2fa4afcf2c6d2fb3102c926e9f989df (patch)
treed0d003c8c9f12b865f0bf8f2015134d7b7031ee5 /fs/cifs/CHANGES
parent61e748015866e48aff91284e3d300c6e3035a87a (diff)
[CIFS] Can not mount with prefixpath if root directory of share is inaccessible
Windows allows you to deny access to the top of a share, but permit access to a directory lower in the path. With the prefixpath feature of cifs (ie mounting \\server\share\directory\subdirectory\etc.) this should have worked if the user specified a prefixpath which put the root of the mount at a directory to which he had access, but we still were doing a lookup on the root of the share (null path) when we should have been doing it on the prefixpath subdirectory. This fixes Samba bug # 5925 Acked-by: Jeff Layton <jlayton@redhat.com> Signed-off-by: Steve French <sfrench@us.ibm.com>
Diffstat (limited to 'fs/cifs/CHANGES')
-rw-r--r--fs/cifs/CHANGES4
1 files changed, 3 insertions, 1 deletions
diff --git a/fs/cifs/CHANGES b/fs/cifs/CHANGES
index 3d848f463c44..5ab6bcce880a 100644
--- a/fs/cifs/CHANGES
+++ b/fs/cifs/CHANGES
@@ -2,7 +2,9 @@ Version 1.56
------------
Add "forcemandatorylock" mount option to allow user to use mandatory
rather than posix (advisory) byte range locks, even though server would
-support posix byte range locks.
+support posix byte range locks. Fix query of root inode when prefixpath
+specified and user does not have access to query information about the
+top of the share.
Version 1.55
------------