This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug stdio/15142] Missing locking in _IO_cleanup
- From: "bugdal at aerifal dot cx" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 14 Feb 2013 20:12:54 +0000
- Subject: [Bug stdio/15142] Missing locking in _IO_cleanup
- Auto-submitted: auto-generated
- References: <bug-15142-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15142
Rich Felker <bugdal at aerifal dot cx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugdal at aerifal dot cx
--- Comment #1 from Rich Felker <bugdal at aerifal dot cx> 2013-02-14 20:12:54 UTC ---
I have two related issues open on the Austin Group bug tracker:
http://austingroupbugs.net/view.php?id=610
http://austingroupbugs.net/view.php?id=611
Unfortunately, I believe the current glibc behavior of not performing
appropriate locking is intentional, so that exit works even when locks
would/should block exit. This is contrary to the requirements of the standard
and harmful to applications that have expectations on the atomicity/integrity
of stdio operations performed under lock.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.