Bug 1424793
Summary: | Missing verification of fcntl return code | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Michael S. <misc> |
Component: | core | Assignee: | Michael S. <misc> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | mainline | CC: | bugs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.11.0 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-05-30 18:44:34 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Michael S.
2017-02-19 14:18:49 UTC
REVIEW: https://review.gluster.org/16671 (Properly verify the return code of fcntl) posted (#1) for review on master by Michael Scherer (misc) COMMIT: https://review.gluster.org/16671 committed in master by Shyamsundar Ranganathan (srangana) ------ commit afe3a0d2869b706a3d5257f39d6acb9cbe856b87 Author: Michael Scherer <misc> Date: Sun Feb 19 15:18:56 2017 +0100 Properly verify the return code of fcntl Coverty scan complain about it, even if in practice, this doesn't seems to have much impact. Change-Id: I513f7d393889625d22dded25ef4c7477f68d1064 BUG: 1424793 Signed-off-by: Michael Scherer <misc> Reviewed-on: https://review.gluster.org/16671 Smoke: Gluster Build System <jenkins.org> Reviewed-by: Shyamsundar Ranganathan <srangana> Tested-by: Nigel Babu <nigelb> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Atin Mukherjee <amukherj> Reviewed-by: Niels de Vos <ndevos> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Poornima G <pgurusid> 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.11.0, please open a new bug report. glusterfs-3.11.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-May/000073.html [2] https://www.gluster.org/pipermail/gluster-users/ |