Bug 1338672 - glibc: GCC 6 enablement for struct sockaddr_storage
Summary: glibc: GCC 6 enablement for struct sockaddr_storage
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: glibc
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: DJ Delorie
QA Contact: Sergey Kolosov
URL:
Whiteboard:
Depends On: 1337291
Blocks: 1413146 1338673
TreeView+ depends on / blocked
 
Reported: 2016-05-23 08:47 UTC by Florian Weimer
Modified: 2017-08-01 18:06 UTC (History)
6 users (show)

Fixed In Version: glibc-2.17-171.el7
Doc Type: Bug Fix
Doc Text:
Cause: New optimizations in GCC 6 may cause portions of struct sockaddr to not be copied in a simple assignment operation when aliasing is enabled. Does not affect GCC prior to version 6, including the bundled RHEL 7 gcc. Consequence: Programs might get invalid data in copied structures. Fix: With this patch, the padding is changed such that there are no undefined regions in the structure, forcing gcc to copy all data. Result: Programs should no longer see uninitialized data in copied struct sockaddrs.
Clone Of: 1337291
Environment:
Last Closed: 2017-08-01 18:06:55 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
GNU Compiler Collection 71120 None None None 2016-05-23 08:47:11 UTC
Red Hat Bugzilla 1338673 None None None Never
Red Hat Product Errata RHSA-2017:1916 normal SHIPPED_LIVE Moderate: glibc security, bug fix, and enhancement update 2017-08-01 18:05:43 UTC
Sourceware 20111 None None None 2016-05-23 08:47:11 UTC

Internal Links: 1338673

Description Florian Weimer 2016-05-23 08:47:12 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 6 errata-xmlrpc 2017-08-01 18:06:55 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/RHSA-2017:1916


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