REVIEW: http://review.gluster.org/9908 (glusterd: Do not use global opinfo in syncop) posted (#1) for review on master by Atin Mukherjee (email@example.com)
COMMIT: http://review.gluster.org/9908 committed in master by Krishnan Parthasarathi (firstname.lastname@example.org)
Author: Atin Mukherjee <email@example.com>
Date: Tue Mar 17 16:47:22 2015 +0530
glusterd: Do not use global opinfo in syncop
Global opinfo should not be referred by syncop framework as it uses local
txn_opinfo for every transaction. There is one place in the codebase where the
global opinfo is set with the local txn_opinfo which can lead to an incorrect
opinfo for an on-going op-sm transaction which refers to the same global opinfo.
Signed-off-by: Atin Mukherjee <firstname.lastname@example.org>
Tested-by: Gluster Build System <email@example.com>
Reviewed-by: Anand Nekkunti <firstname.lastname@example.org>
Reviewed-by: Krishnan Parthasarathi <email@example.com>
Tested-by: Krishnan Parthasarathi <firstname.lastname@example.org>
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.7.0, please open a new bug report.
glusterfs-3.7.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.