Yes, You are right. Patch for this bug merged in upstream in both master and release-3.7. 3.7 : http://review.gluster.org/#/c/13494/ master : http://review.gluster.org/#/c/13319/.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
This issue is not seen with 3.1.3 build. Verified in gluster-3.7.9-10.
Based on comment#6, I am moving this to Closed-CurrentRelease.