From: Ulrich Drepper <drepper@redhat.com>
Date: Mon, 9 Feb 2004 20:08:44 +0000 (+0000)
Subject: (_IO_cleanup): Do not use locking when flushing the buffers.  Some thread might be... 
X-Git-Tag: upstream/2.30~18322
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=64f01020838a382d833254297f650d4a55933bde;p=external%2Fglibc.git

(_IO_cleanup): Do not use locking when flushing the buffers.  Some thread might be using a stream.
---

diff --git a/libio/genops.c b/libio/genops.c
index 58dac00..5b65e76 100644
--- a/libio/genops.c
+++ b/libio/genops.c
@@ -942,7 +942,9 @@ _IO_unbuffer_write ()
 int
 _IO_cleanup ()
 {
-  int result = INTUSE(_IO_flush_all) ();
+  /* We do *not* want locking.  Some threads might use streams but
+     that is there problem, we flush them underneath them.  */
+  int result = _IO_flush_all_lockp (0);
 
   /* We currently don't have a reliable mechanism for making sure that
      C++ static destructors are executed in the correct order.