hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Agarwal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5849) Removing ACL from an inode fails if it has only a default ACL.
Date Fri, 31 Jan 2014 17:56:09 GMT

    [ https://issues.apache.org/jira/browse/HDFS-5849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887944#comment-13887944
] 

Arpit Agarwal commented on HDFS-5849:
-------------------------------------

Thanks for the detailed explanation Chris.

+1 for the patch.

> Removing ACL from an inode fails if it has only a default ACL.
> --------------------------------------------------------------
>
>                 Key: HDFS-5849
>                 URL: https://issues.apache.org/jira/browse/HDFS-5849
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: HDFS ACLs (HDFS-4685)
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>         Attachments: HDFS-5849.1.patch
>
>
> When removing an ACL, the logic must restore the group permission previously stored in
an ACL entry back into the group permission bits.  The logic for this in {{AclTransformation#removeINodeAcl}}
assumes that the group entry must be found in the former ACL.  This is not the case when removing
the ACL from an inode that only had a default ACL and not an access ACL.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message