Bug 182066 - GFS with default ACL on new folder is not applied ?!
GFS with default ACL on new folder is not applied ?!
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: gfs-kmod (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Abhijith Das
GFS Bugs
Depends On:
  Show dependency treegraph
Reported: 2006-02-19 22:40 EST by Andrey
Modified: 2010-01-11 22:23 EST (History)
0 users

See Also:
Fixed In Version: RHBA-2006-0561
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-08-10 17:35:00 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2006:0561 normal SHIPPED_LIVE GFS-kernel bug fix update 2006-08-10 00:00:00 EDT

  None (edit)
Description Andrey 2006-02-19 22:40:03 EST
Description of problem:     
GFS with default ACL on new folder is not applied.    
Version-Release number of selected component (if applicable):     
How reproducible:     
   Obligatory condition - a new folder, use default ACL. 
    The mistake generates only once. 
    Then any actions with ACL above a folder are always successful. 
Steps to Reproduce: 
1. I use GFS with ACL     
    # mount | grep gfs     
    /dev/sda5 on /home type gfs (rw,noatime,acl)      
2.  # cd /home      
    # mkdir test_acl      
    If now to apply default ACL on folder we receive a errors.      
    # setfacl -d -m g:dc_local:rwx test_acl/      
    setfacl: test_acl: Operation not permitted      
3.  After that the same without errors!?      
    # setfacl -d -m g:dc_local:rwx test_acl/      
    # getfacl test_acl      
# file: test_acl      
# owner: root      
# group: root      
Actual results:     
Expected results:     
Additional info: 
     The mistake generates only once. 
     Then any actions with ACL above a folder are always successful.
Comment 1 Abhijith Das 2006-03-13 17:23:24 EST
Committed fix to RHEL4 and STABLE cvs branches. The return code while setting
default ACLs was not being propagated. Instead an EPERM was being returned all
the time.
Comment 4 Red Hat Bugzilla 2006-08-10 17:35:08 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

Comment 5 Nate Straz 2007-12-13 12:42:29 EST
Moving all RHCS ver 5 bugs to RHEL 5 so we can remove RHCS v5 which never existed.
Comment 6 Nate Straz 2007-12-19 15:06:29 EST
Moving all closed bugs to gfs-kmod to match the rpm name.  GFS-kernel will be

Note You need to log in before you can comment on or make changes to this bug.