Description of problem: Following static analysis issue is reported. xlators/performance/io-threads/src/io-threads.c:350: overrun-local: Overrunning array "gf_fop_list" of 49 8-byte elements at element index 49 (byte offset 392) using index "stub->fop" (which evaluates to 49). Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/8939 (performance/io-threads: Fix static analysis error) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)
COMMIT: http://review.gluster.org/8939 committed in master by Vijay Bellur (vbellur) ------ commit eea806646216f5e5a91fd35a4e138e193e3b6fac Author: Pranith Kumar K <pkarampu> Date: Fri Oct 17 11:46:46 2014 +0530 performance/io-threads: Fix static analysis error stub->fop can be more than FOP_MAX is what static analysis is complaining. This patch doesn't allow any 'log' to be printed in the case fop value is not in the definied range. It gives EINVAL instead. Change-Id: I293381e2c1ad0ab45154b0192a637612becaf744 BUG: 1153935 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/8939 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
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