Bug 1318296

Summary: should find_library("c") be used instead of find_library("libc") in geo-replication/syncdaemon/libcxattr.py?
Product: [Community] GlusterFS Reporter: Roman Tereshonkov <tereshonkov.roman>
Component: geo-replicationAssignee: Saravanakumar <sarumuga>
Status: CLOSED WONTFIX QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 3.6.9CC: bugs, mselvaga, otira.fuu
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1352423 (view as bug list) Environment:
Last Closed: 2016-08-01 09:25:04 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:    
Bug Blocks: 1352423    

Description Roman Tereshonkov 2016-03-16 13:08:01 UTC
Description of problem:

In geo-replication/syncdaemon/libcxattr.py
is it right to use 
libc = CDLL(find_library("libc"))
instead of 
libc = CDLL(find_library("c"))


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Saravanakumar 2016-07-04 08:04:06 UTC
Patch posted in upstream:
http://review.gluster.org/#/c/14852/

Comment 2 Saravanakumar 2016-08-01 09:25:04 UTC
This is not a security bug, not going to fix this in 3.6.x because of http://www.gluster.org/pipermail/gluster-users/2016-July/027682.html

As mentioned in comment#1, patch is posted and merged in upstream.