RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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

Hi,

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

Thanks.