Bug 1366226 - Move alloca0 definition to common-utils
Summary: Move alloca0 definition to common-utils
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ravishankar N
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-11 10:24 UTC by Ravishankar N
Modified: 2017-03-27 18:19 UTC (History)
1 user (show)

Fixed In Version: glusterfs-3.9.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-27 18:19:04 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Ravishankar N 2016-08-11 10:24:23 UTC
libglusterfs: move alloca0 definition to common-utils

    ...and remove their definitons from EC and AFR.
    Also `s/alloca+memset0/alloca0` wherever it is used.

Comment 1 Vijay Bellur 2016-08-11 10:30:06 UTC
REVIEW: http://review.gluster.org/15147 (libglusterfs: move alloca0 definition to common-utils) posted (#1) for review on master by Ravishankar N (ravishankar)

Comment 2 Vijay Bellur 2016-08-12 08:53:27 UTC
COMMIT: http://review.gluster.org/15147 committed in master by Pranith Kumar Karampuri (pkarampu) 
------
commit df6a127b4dbb96dd970d255635ccfeae17a38186
Author: Ravishankar N <ravishankar>
Date:   Wed Aug 10 11:24:19 2016 +0530

    libglusterfs: move alloca0 definition to common-utils
    
    ...and remove their definitons from EC and AFR.
    Also `s/alloca+memset0/alloca0` wherever it is used.
    
    Change-Id: I3b71e596d12a7d8900f5d761af6b98305c8874d5
    BUG: 1366226
    Signed-off-by: Ravishankar N <ravishankar>
    Reviewed-on: http://review.gluster.org/15147
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    CentOS-regression: Gluster Build System <jenkins.org>

Comment 3 Shyamsundar 2017-03-27 18:19:04 UTC
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.9.0, please open a new bug report.

glusterfs-3.9.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/gluster-users/2016-November/029281.html
[2] https://www.gluster.org/pipermail/gluster-users/


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