Description of problem: Coverity scan result: https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-07-21-88af8d7a/html/ EC Issue: https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-07-21-88af8d7a/html/1/7ec-common.c.html#error:12 Version-Release number of selected component (if applicable): master How reproducible: Steps to Reproduce: Coverity Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/17860 (cluster/ec: Fix coverity issue) posted (#1) for review on master by Anonymous Coward
REVIEW: https://review.gluster.org/17860 (cluster/ec: Fix coverity issue) posted (#2) for review on master by Sunny Kumar
REVIEW: https://review.gluster.org/17860 (cluster/ec: Fix coverity issue) posted (#3) for review on master by Sunny Kumar
REVIEW: https://review.gluster.org/18186 (cluster/ec: fix for BAD_SHIFT, follow-up patch) posted (#1) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: https://review.gluster.org/18186 (cluster/ec: fix for BAD_SHIFT, follow-up patch) posted (#2) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: https://review.gluster.org/18186 (cluster/ec: fix for BAD_SHIFT, follow-up patch) posted (#3) for review on master by Kaleb KEITHLEY (kkeithle)
COMMIT: https://review.gluster.org/18186 committed in master by Kaleb KEITHLEY (kkeithle) ------ commit 6b30347f65c9590fa1b636e4aed0471dc8eeff07 Author: Kaleb S. KEITHLEY <kkeithle> Date: Sat Sep 2 09:49:06 2017 -0400 cluster/ec: fix for BAD_SHIFT, follow-up patch Address comments to https://review.gluster.org/18067, (Change-Id I86e15d12939c610c99f5f96c551bb870df20f4b4) Which was posted as an RFC as an example of a possible alternative fix to https://review.gluster.org/17860 (Change-Id I28a3bdd4a357526dba0cf84c262919c05cfa173e) An alternative fix that preserved the unsignedness of the indexes throughout, obviating the need to check its value before using it to shift. (shift by negative number is undefined, as is shift by more bits than in the type.) BUG: 1474309 Change-Id: I46fe9cec140d3397463780748f6876251acb06dd Signed-off-by: Kaleb S. 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.13.0, please open a new bug report. glusterfs-3.13.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://lists.gluster.org/pipermail/announce/2017-December/000087.html [2] https://www.gluster.org/pipermail/gluster-users/