Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1615385

Summary: glusterd segfault - memcpy () at /usr/include/bits/string3.h:51
Product: [Community] GlusterFS Reporter: Mohit Agrawal <moagrawa>
Component: glusterdAssignee: Mohit Agrawal <moagrawa>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: high    
Version: mainlineCC: amukherj, atumball, bmekala, bugs, jstrunk, rhs-bugs, sankarshan, sheggodu, srangana, storage-qa-internal, vbellur, vdas
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-6.x Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1608507 Environment:
Last Closed: 2019-05-11 11:44:36 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: 1608507    
Bug Blocks:    

Comment 1 Worker Ant 2018-08-13 13:35:42 UTC 
REVIEW: https://review.gluster.org/20695 (glusterd: glusterd segfault at the time of running profile operation) posted (#3) for review on master by MOHIT AGRAWAL
Comment 2 Atin Mukherjee 2018-12-17 09:42:12 UTC 
Fixed through:

commit e48678567a5fb01166a065f9e192b80e721e4181
Author: Sanju Rakonde <srakonde>
Date:   Thu Nov 8 18:50:18 2018 +0530

    glusterd: migrating profile commands to mgmt_v3 framework
    
    Current profile commands use the op_state machine framework.
    Porting it to use the mgmt_v3 framework.
    
    The following tests were performed on the patch:
    case 1:
    1. On a 3 node cluster, created and started 3 volumes
    2. Mounted all the three volumes and wrote some data
    3. Started profile operation for all the volumes
    4. Ran "gluster v status" from N1,
           "gluster v profile <volname1> info" form N2,
           "gluster v profile <volname2> info" from N3 simultaneously in a
       loop for around 10000 times
    5. Didn't find any cores generated.
    
    case 2:
    1. Repeat the steps 1,2 and 3 from case 1.
    2. Ran "gluster v status" from N1,
           "gluster v profile <volname1> info" form N2(terminal 1),
           "gluster v profile <volname2> info" from N2(terminal 2)
       simultaneously in a loop.
    3. No cores were generated.
    
    fixes: bz#1654181
    Change-Id: I83044cf5aee3970ef94066c89fcc41783ed468a6
    Signed-off-by: Sanju Rakonde <srakonde>