Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1570582 - Build is failed due to access rpc->refcount in wrong way in quota.c
Build is failed due to access rpc->refcount in wrong way in quota.c
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: quota (Show other bugs)
3.4
All All
unspecified Severity urgent
: ---
: RHGS 3.4.0
Assigned To: Mohit Agrawal
Rajesh Madaka
:
Depends On:
Blocks: 1503137
  Show dependency treegraph
 
Reported: 2018-04-23 05:38 EDT by Mohit Agrawal
Modified: 2018-09-04 02:48 EDT (History)
8 users (show)

See Also:
Fixed In Version: glusterfs-3.12.2-9
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-09-04 02:47:18 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:2607 None None None 2018-09-04 02:48 EDT

  None (edit)
Description Mohit Agrawal 2018-04-23 05:38:49 EDT
Description of problem:
In upstream patch(https://review.gluster.org/#/c/19734/) to access 
rpc->refcount call GF_ATOMIC_GET macros but in downstream refcount is declared
as an integer in rpc_clnt, not gf_atomic_t so the downstream build is failed after merged 
the same patch from the commit https://code.engineering.redhat.com/gerrit/#/c/136229/

Version-Release number of selected component (if applicable):


How reproducible:
Compiled downstream build on centos

Steps to Reproduce:
1.
2.
3.

Actual results:
build is failed

Expected results:
The build should not fail.

Additional info:
Comment 9 Rajesh Madaka 2018-05-21 06:33:41 EDT
Based on comment 6 moving this bug to verified state
Comment 11 errata-xmlrpc 2018-09-04 02:47:18 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2607

Note You need to log in before you can comment on or make changes to this bug.