[
https://issues.apache.org/jira/browse/HDFS-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995598#comment-13995598
]
Andrew Wang commented on HDFS-6373:
-----------------------------------
Related, I also found this page, which indicates that having ACLs on symlinks
is dubious:
http://0xced.blogspot.com/2009/03/chmod-acl-and-symbolic-links_23.html
This makes sense to me, since symlink permissions are always ignored. Linux
actually doesn't even let you change symlink permissions, though it is allowed
by the Unix spec. [~cnauroth], could you comment on whether this was
intentional, or just an oversight? It seems like we might want to remove
ACLs-on-symlinks, which is compatible since symlinks are still hard-disabled.
> Remove support for extended attributes on symlinks
> --------------------------------------------------
>
> Key: HDFS-6373
> URL: https://issues.apache.org/jira/browse/HDFS-6373
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Reporter: Andrew Wang
>
> Looking in the Linux source code, we see the following:
> http://lxr.linux.no/linux+v3.14.3/fs/xattr.c
> {code}
> 60 /*
> 61 * In the user.* namespace, only regular files and directories
> can have
> 62 * extended attributes. For sticky directories, only the owner and
> 63 * privileged users can write attributes.
> 64 */
> {code}
> We should consider removing {{XAttrFeature}} from {{INodeSymlink}}.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
