Description of problem: Glusterfs code does not check xlator_mem_acct_init() return in some places, thus fails to capture wrong memory accounting initialization. Version-Release number of selected component (if applicable): GlusterFS 3.5 How reproducible: N/A Steps to Reproduce: N/A Actual results: Expected results: It should check the return for failures/success.
REVIEW: http://review.gluster.org/7728 (mem_acct : Check return value of xlator_mem_acct_init()) posted (#8) for review on master by Humble Devassy Chirammal (humble.devassy)
REVIEW: http://review.gluster.org/7728 (mem_acct : Check return value of xlator_mem_acct_init()) posted (#9) for review on master by Humble Devassy Chirammal (humble.devassy)
REVIEW: http://review.gluster.org/7728 (mem_acct : Check return value of xlator_mem_acct_init()) posted (#10) for review on master by Humble Devassy Chirammal (humble.devassy)
REVIEW: http://review.gluster.org/7728 (mem_acct : Check return value of xlator_mem_acct_init()) posted (#11) for review on master by Humble Devassy Chirammal (humble.devassy)
REVIEW: http://review.gluster.org/7728 (mem_acct : Check return value of xlator_mem_acct_init().) posted (#12) for review on master by Humble Devassy Chirammal (humble.devassy)
COMMIT: http://review.gluster.org/7728 committed in master by Vijay Bellur (vbellur) ------ commit 656711d935000c161012c25340dbd65a59999dc3 Author: Humble Chirammal <hchiramm> Date: Fri May 9 15:30:04 2014 +0530 mem_acct : Check return value of xlator_mem_acct_init(). some code does not check xlator_mem_acct_init() return, thus fails to capture wrong memory accounting initialization. This patch fix the same. Change-Id: I01eab19d6cef472afd850b0f964132c01523492a BUG: 1123768 Signed-off-by: Humble Chirammal <hchiramm> Reviewed-on: http://review.gluster.org/7728 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Niels de Vos <ndevos> Reviewed-by: Kaleb KEITHLEY <kkeithle>
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