Description of problem: We call __iobuf_ref directly without taking lock and without going through iobuf_ref in some places. It does not cause any functional problems but going through the right way will help later in accounting refs.
REVIEW: http://review.gluster.org/9812 (iobuf: Do not call __iobuf_ref directly.) posted (#1) for review on master by Raghavendra Talur (rtalur)
REVIEW: http://review.gluster.org/9812 (iobuf: Do not call __iobuf_ref directly.) posted (#2) for review on master by Raghavendra Talur (rtalur)
REVIEW: http://review.gluster.org/9812 (iobuf: Do not call __iobuf_ref directly) posted (#3) for review on master by Raghavendra Talur (rtalur)
COMMIT: http://review.gluster.org/9812 committed in master by Vijay Bellur (vbellur) ------ commit 10b4ecb85c5009c6c7b9422bd5299ba43d8448a1 Author: Raghavendra Talur <rtalur> Date: Thu Mar 5 18:19:30 2015 +0530 iobuf: Do not call __iobuf_ref directly iobuf_get will be creating the iobuf and hence lock is not necessary to increment ref. However, it is a good practice to call iobuf_ref instead of __iobuf_ref so that we have a single point to get refs and this can be used later to do mem accounting etc. Change-Id: I1fd328c3c463c23fd5f6df505ccb5c86f6207f28 BUG: 1199075 Signed-off-by: Raghavendra Talur <rtalur> Reviewed-on: http://review.gluster.org/9812 Reviewed-by: Niels de Vos <ndevos> Tested-by: 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.7.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user