----- Original Message ----- | The function __gfs2_xattr_set() will return -ENODATA when called to | remove a xattr that does not exist. The result is that setfacl will | show an exit status of 1 when called to set only a file's mode bits | (on a file with no ACLs), despite succeeding. A "No data available" | error will be printed as well. | | To fix this return 0 instead, except when the XATTR_REPLACE flag is | set, in which case -ENODATA is appropriate. This is consistent with | how most other xattr setting functions work, in other filesystems. | | Signed-off-by: Ernesto A. Fernández <[email protected]> | --- Hi,
Thanks. This is now pushed to the for-next branch of the linux-gfs2 tree: https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs/gfs2?h=for-next&id=54aae14beee6a6e9f72358f1873b3e497029c41d Regards, Bob Peterson Red Hat File Systems
