From: Jean-Pierre A. <jea...@wa...> - 2013-08-10 12:13:38
|
Michael j Theall wrote: > I'm trying to test xattrs on symlinks in my filesystem, but only > llistxattr actually invokes listxattr in fuse_lowlevel_ops. Any attempt to > use lgetxattr, lsetxattr, or lremovexattr comes back immediately with > EPERM without any apparent attempt to consult my filesystem. They do go > through with regular files and directories, but not with symlinks, > regardless of whether the link is broken or not. The permissions for the > symlink are 777, and I'm using FUSE 2.8.3 lowlevel API on a 2.6.32 kernel. > Any ideas? From http://linux.die.net/man/5/attr : For regular files and directories the file permission bits define access to the file's contents, while for device special files they define access to the device described by the special file. The file permissions of symbolic links are not used in access checks. These differences would allow users to consume filesystem resources in a way not controllable by disk quotas for group or world writable special files and directories. 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 |