[
https://issues.apache.org/jira/browse/HDFS-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997151#comment-13997151
]
Andrew Wang commented on HDFS-6374:
-----------------------------------
Could we add a unit test to verify this behavior? Check out some of the doAs
examples in other tests.
I'm also not sure what the sticky bit has to do with this. Making all modify
operations require the owner essentially does the sticky bit, and xattr
operations from what I understand should be checking the permissions of the
inode itself, not its parent directory. So, the intent of this patch seems
right to me.
> setXAttr should require the user to be the owner of the file or directory
> -------------------------------------------------------------------------
>
> Key: HDFS-6374
> URL: https://issues.apache.org/jira/browse/HDFS-6374
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Affects Versions: HDFS XAttrs (HDFS-2006)
> Reporter: Andrew Wang
> Assignee: Charles Lamb
> Attachments: HDFS-6374.1.patch, HDFS-6374.2.patch
>
>
> From the attr(5) manpage:
> {noformat}
> For this reason, extended user attributes are only allowed for regular
> files and directories, and access to extended user attributes is
> restricted to the owner and to users with appropriate capabilities for
> directories with the sticky bit set (see the chmod(1) manual page for
> an explanation of Sticky Directories).
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
