Bug 1323134

Summary: glibc: stdio race condition causes crash during process shutdown
Product: Red Hat Enterprise Linux 6 Reporter: Florian Weimer <fweimer>
Component: glibcAssignee: glibc team <glibc-bugzilla>
Status: CLOSED WONTFIX QA Contact: qe-baseos-tools-bugs
Severity: low Docs Contact:
Priority: low    
Version: 6.8CC: ashankar, christopher.a.dickens, cww, fweimer, mnewsome, pandrade, pfrankli
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-15 19:07:16 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:
Attachments:
Description Flags
tst-stdio-exit-lock.c none

Description Florian Weimer 2016-04-01 11:09:24 UTC 
Created attachment 1142511 [details]
tst-stdio-exit-lock.c

The test case for this upstream bug:

  http://sourceware.org/bugzilla/show_bug.cgi?id=12847

exercises a different code path as well, and crashes occasionally even if swbz#12847 is fixed.

This was corrected in this upstream commit, which is currently missing in Red Hat Enterprise Linux 6:

commit f22e10748fbabbf07161eb7a5540b8c0e18553c4
Author: Ulrich Drepper <drepper>
Date:   Fri Sep 9 16:15:25 2011 -0400

    Don't lock string streams in stream cleanup code

The attached test case triggers this bug about 80% of the time on my test VM.  It has to be run in a shell script, like this:

set -e
for x in `seq 1 100` ; do
  ./tst-stdio-exit-lock
done
Comment 2 Chris Dickens 2016-04-01 16:56:03 UTC 
Hi,

This bug is not relevant to my use case as described in bug 1275384.

Thanks.