Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 30 Jan 2014 07:20:09 +0000 (UTC)
From: "Chris Nauroth (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12692135.1391028276456.8869.1391066409442@arcas>
In-Reply-To: <JIRA.12692135.1391028276456@arcas>
References: <JIRA.12692135.1391028276456@arcas>
Subject: [jira] [Work started] (HDFS-5849) Removing ACL from an inode fails
 if it has only a default ACL.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-5849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on HDFS-5849 started by Chris Nauroth.

> 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)