Bug 1698435 - glusterfs-libs: usage of inet_addr() may impact IPv6
Summary: glusterfs-libs: usage of inet_addr() may impact IPv6
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: core
Version: rhgs-3.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: RHGS 3.5.0
Assignee: Rinku
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1696809 1721385
TreeView+ depends on / blocked
 
Reported: 2019-04-10 11:17 UTC by Milind Changire
Modified: 2020-02-27 09:39 UTC (History)
8 users (show)

Fixed In Version: glusterfs-6.0-8
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1721385 (view as bug list)
Environment:
Last Closed: 2019-10-30 12:20:50 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:3249 0 None None None 2019-10-30 12:21:14 UTC

Description Milind Changire 2019-04-10 11:17:15 UTC
Description of problem:
RRPMDiff has a raised a warning:
usr/lib64/libglusterfs.so.0.0.1 on x86_64 uses function inet_addr, which may impact IPv6 support

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 5 Rinku 2019-06-17 05:57:41 UTC
REVIEW:  https://review.gluster.org/#/c/glusterfs/+/22866/  (core: replace inet_addr with inet_pton) posted (#1) for review on master by Rinku Kothiya

Comment 6 Atin Mukherjee 2019-06-24 15:21:41 UTC
We saw this error popping up in eventing component which is used in RHHI. So recommend fixing it.

Comment 13 SATHEESARAN 2019-10-14 09:28:59 UTC
Tested with glusterfs-6.0-15.el7rhgs

1. RHGS nodes are set with pure IPV6
2. Glusterd configured to support inet v6
3. Gluster peer probe done with IPv6
4. Gluster volume is created with the same IPV6
5. Gluster volume is fuse mounted with special mount option and then
I/O done.
6. Geo-rep session also initiated and completed to another gluster IPv6 cluster

No errors seen.

Comment 15 errata-xmlrpc 2019-10-30 12:20:50 UTC
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/RHEA-2019:3249


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