Our QA team found an interesting issue while testing Bug 8857 - however it seems like a separate issue because this one happens when using SMB2 and the other bug I filed was hit when SMB2 was not being used. We're using Samba 3.6.4 with Jeremy's patch from bug 8857 applied. It works as expected when using Windows Server 2008 as a client but fails when using Windows 7, both against the same samba server and share. Given a directory structure like: "folder a\folder b\folder c" where the user has full control of "folder a" and "folder b", but only traverse rights to "folder b" and none of the dirs are inheriting the permissions from the parent. Create a new folder "folder d" inside "folder c" allowing "folder d" to inherit from its parent. As the user with only traverse rights to "folder b" enter the full path to the destination in Windows explorer ("\\host\share a\folder a\folder b\folder c\folder d"). If both SMB2 and acl_xattr are enabled this will fail on Windows 7. What's also interesting is that if one was to directly enter "\\host\share a\folder a\folder b\folder c" and then use explorer to navigate into "folder d" it works.
Created attachment 7485 [details] level 10 logs and sample config files I'm attaching level 10 logs and configs from 3 test runs The three runs were: xattr_smb2 : both features enabled smb2_only : only SMB2 enabled, acl_xattr disabled xattr_only : only acl_xattr enabled, SMB2 disabled Please let me know if there is any other information I can provide.
Sorry, I just noticed a typo in my original bug report. I the 3rd paragraph it should say: Given a directory structure like: "folder a\folder b\folder c" where the user has full control of "folder a" and "folder c", but only traverse rights to "folder b" and none of the dirs are inheriting the permissions from the parent. Create a new folder "folder d" inside "folder c" allowing "folder d" to inherit from its parent. I apologize for the noise.