Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1322544 - Segmentation violation can occur within glibc if fork() is used in a multi-threaded application
Segmentation violation can occur within glibc if fork() is used in a multi-th...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: glibc (Show other bugs)
7.3
All Linux
unspecified Severity medium
: rc
: ---
Assigned To: Martin Sebor
Sergey Kolosov
: Patch
Depends On: 1275384
Blocks: 1413146
  Show dependency treegraph
 
Reported: 2016-03-30 13:14 EDT by Carlos O'Donell
Modified: 2017-08-01 14:06 EDT (History)
10 users (show)

See Also:
Fixed In Version: glibc-2.17-175.el7
Doc Type: Bug Fix
Doc Text:
Multithreaded applications no longer crash when calling dprintf() and fork() concurrently Multithreaded applications that use the dprintf() and fork() *glibc* functions concurrently could previously terminate unexpectedly with a segmentation fault. With this update, the fork() implementation has been fixed to ignore temporary streams created by dprintf(), and the described problem no longer occurs.
Story Points: ---
Clone Of: 1275384
Environment:
Last Closed: 2017-08-01 14:06:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Sourceware 12847 None None None 2016-03-30 13:14 EDT
Red Hat Product Errata RHSA-2017:1916 normal SHIPPED_LIVE Moderate: glibc security, bug fix, and enhancement update 2017-08-01 14:05:43 EDT

  None (edit)
Comment 2 Florian Weimer 2016-10-11 16:05:48 EDT
A fix for this issue should also pick up the fix for bug 1323134.
Comment 9 errata-xmlrpc 2017-08-01 14:06:55 EDT
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.