Bug 1338673

Summary: glibc: GCC 6 enablement for struct sockaddr_storage [el6]
Product: Red Hat Enterprise Linux 6 Reporter: Florian Weimer <fweimer>
Component: glibcAssignee: DJ Delorie <dj>
Status: CLOSED ERRATA QA Contact: Sergey Kolosov <skolosov>
Severity: unspecified Docs Contact: Mark Flitter <mflitter>
Priority: unspecified    
Version: 6.9CC: ashankar, codonell, dj, fweimer, jridky, kdudka, mcermak, mflitter, mnewsome, pfrankli, skolosov
Target Milestone: rcKeywords: Patch, Reopened
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: glibc-2.12-1.207.el6 Doc Type: Bug Fix
Doc Text:
Resolution for gcc compatibility issue with "sockaddr_in" The default RHEL 6 compiler has rules about how to copy "struct sockaddr_in" that are substantially different to those used by later versions of gcc (E.g. the tools provided with Red Hat Developer Toolset). This caused corrupted sockaddr_in overlays when using newer compilers. This update changes the way the "unused" portions of the sockaddr_in structure are defined. Now, newer versions of gcc will copy them correctly. Note that -fno-strict-aliasing is still required for compiling such sources.
Story Points: ---
Clone Of: 1337291 Environment:
Last Closed: 2017-03-21 10:36:40 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:
Bug Depends On: 1337291, 1338672    
Bug Blocks: 1361283    

Description Florian Weimer 2016-05-23 08:50:27 UTC
+++ This bug was initially created as a clone of Bug #1337291 +++

The current struct sockaddr_storage definition causes problems with GCC 6 which are not fixed by -fno-strict-aliasing.  We need to backport a definition which compensates for this.

Comment 14 errata-xmlrpc 2017-03-21 10:36:40 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://rhn.redhat.com/errata/RHSA-2017-0680.html