Bug 1400802
Summary: | glusterfs_ctx_defaults_init is re-initializing ctx->locks | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | rjoseph |
Component: | cli | Assignee: | rjoseph |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.8 | CC: | bugs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.8.7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1397419 | Environment: | |
Last Closed: | 2016-12-14 07:13:24 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: | |||
Bug Depends On: | 1397419 | ||
Bug Blocks: |
Description
rjoseph
2016-12-02 06:35:08 UTC
REVIEW: http://review.gluster.org/16001 (glusterfsd: glusterfs_ctx_defaults_init should not re-initialize ctx->locks) posted (#1) for review on release-3.8 by Rajesh Joseph (rjoseph) REVIEW: http://review.gluster.org/16003 (cli: glusterfs_ctx_defaults_init should not re-initialize ctx->locks) posted (#1) for review on release-3.8 by Rajesh Joseph (rjoseph) COMMIT: http://review.gluster.org/16003 committed in release-3.8 by Vijay Bellur (vbellur) ------ commit 48031e69fd8928e79b3ae4ae49640530e131e2fd Author: Rajesh Joseph <rjoseph> Date: Tue Nov 22 01:48:26 2016 +0530 cli: glusterfs_ctx_defaults_init should not re-initialize ctx->locks glusterfs_ctx_new already initialize ctx->locks therefore the second initialization in glusterfs_ctx_defaults_init does not make sense. > Reviewed-on: http://review.gluster.org/15904 > Smoke: Gluster Build System <jenkins.org> > NetBSD-regression: NetBSD Build System <jenkins.org> > CentOS-regression: Gluster Build System <jenkins.org> > Reviewed-by: Atin Mukherjee <amukherj> (cherry picked from commit 8df8a2308fcf5efda638f160428158127930d00f) Change-Id: I8a44bed13af20e60e8bafb05360e88c0b237056c BUG: 1400802 Signed-off-by: Rajesh Joseph <rjoseph> Reviewed-on: http://review.gluster.org/16003 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> 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.8.7, please open a new bug report. glusterfs-3.8.7 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://www.gluster.org/pipermail/packaging/2016-December/000226.html [2] https://www.gluster.org/pipermail/gluster-users/ REVIEW: http://review.gluster.org/16249 (cli: glusterfs_ctx_defaults_init should not re-initialize ctx->locks) posted (#1) for review on release-3.8-fb by Kevin Vigor (kvigor) |