Bug 9677 - wrong ACL with Samba => 3.4.x
Summary: wrong ACL with Samba => 3.4.x
Status: NEW
Alias: None
Product: Samba 3.6
Classification: Unclassified
Component: File services (show other bugs)
Version: unspecified
Hardware: All Linux
: P5 normal
Target Milestone: ---
Assignee: Volker Lendecke
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-25 15:44 UTC by Alexander Födisch
Modified: 2013-04-11 09:43 UTC (History)
2 users (show)

See Also:

Attachments
Logfile log level 10 (534.83 KB, text/plain)
2013-02-26 08:04 UTC, Alexander Födisch 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Födisch 2013-02-25 15:44:38 UTC 
When a file is created with samba 3.5.x or 3.6.x, it is created effective read-only:

~ # getfacl Microsoft\ Word-Dokument\ \(neu\).docx
# file: Microsoft\040Word-Dokument\040(neu).docx
# owner: root
# group: 11816
user::rwx
user:11582:rwx            #effective:r--
group::rwx                #effective:r--
mask::r--
other::---


The ACL settings for the parent directory are ok:

~ # getfacl .
# file: .
# owner: root
# group: 11816
user::rwx
user:11582:rwx
group::rwx
mask::rwx
other::---
default:user::rwx
default:user:11582:rwx
default:group::rwx
default:mask::rwx
default:other::---



The same Samba configuration on the same filesystem (GPFS) running with Samba 3.4.x is working correctly:

[share]
        read only               = no
        inherit acls            = yes
        inherit owner           = yes
        inherit permissions     = yes
        nt acl support          = yes
Comment 1 Alexander Födisch 2013-02-26 08:04:03 UTC 
Created attachment 8583 [details]
Logfile log level 10

logfile while creating a new file on Windows 7 client
Comment 2 Alexander Födisch 2013-04-11 09:43:23 UTC 
workaround found: we set "inherit acl = no" and it works. There must be a problem when "inherit acl = yes" is set and default ACLs are used(?)