Description of problem: listxattr is called as part of glfs_h_getxattrs() when NULL is passed to name field. but glfs_h_getxattrs_common() inside it will error out if name is NULL
REVIEW: http://review.gluster.org/13482 (gfapi : fixing listxattr call for handle ops) posted (#1) for review on master by jiffin tony Thottan (jthottan)
REVIEW: http://review.gluster.org/13482 (gfapi : fixing listxattr call for handle ops) posted (#2) for review on master by jiffin tony Thottan (jthottan)
COMMIT: http://review.gluster.org/13482 committed in master by Niels de Vos (ndevos) ------ commit 0bc54f3ea7a56040df4a67b8626200b47fa3d779 Author: Jiffin Tony Thottan <jthottan> Date: Mon Feb 22 16:50:12 2016 +0530 gfapi : fixing listxattr call for handle ops Currently listxattr is called as part of glfs_h_getxattrs() when NULL is passed to name field, but glfs_h_getxattrs_common() inside it will error out if name is NULL. Therefore listxattr is broken for handle ops. Change-Id: I9ced6e33525e1e1a50298972e4922c954fc2b223 BUG: 1310620 Signed-off-by: Jiffin Tony Thottan <jthottan> Reviewed-on: http://review.gluster.org/13482 Reviewed-by: Niels de Vos <ndevos> Smoke: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user