Description of problem: Currently triggering signing for a file (explicit signing by bitd) is based on overloading writev(). This is a bit dangerous and not clean. Better to move it to setxattr() path (with a special key identified by bitd and stub). Version-Release number of selected component (if applicable): mainline
REVIEW: http://review.gluster.org/10942 (features/bitrot: stub improvements and fixes) posted (#1) for review on master by Venky Shankar (vshankar)
patch merged in upstream master: http://review.gluster.org/#/c/10942/ don't know why the commit didn't update the bz.
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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