fb6d68
From 4da80956418bbe1fdc23cad0b1cbb24cd7b87609 Mon Sep 17 00:00:00 2001
fb6d68
From: =?UTF-8?q?Patrik=20H=C3=A4gglund?= <patrik.h.hagglund@ericsson.com>
fb6d68
Date: Sat, 2 Feb 2013 20:21:05 +0100
fb6d68
Subject: [PATCH] PATCH [perl #106212] Add PL_perlio_mutex to
fb6d68
 atfork_lock/unlock
fb6d68
fb6d68
Using threads + fork() on Linux, and IO operations in the threads, the
fb6d68
PL_perlio_mutex may be left in a locked state at the call of fork(),
fb6d68
potentially leading to deadlock in the child process at subsequent IO
fb6d68
operations. (Threads are pre-empted and not continued in the child
fb6d68
process after the fork.)
fb6d68
fb6d68
Therefore, ensure that the PL_perlio_mutex is unlocked in the child
fb6d68
process, right after fork(), by using atfork_lock/unlock.
fb6d68
fb6d68
(The RT text gives ways to reproduce the problem, but are not easily
fb6d68
added to Perl's test suite)
fb6d68
---
fb6d68
 util.c | 6 ++++++
fb6d68
 1 file changed, 6 insertions(+)
fb6d68
fb6d68
diff --git a/util.c b/util.c
fb6d68
index 5c695b8..75381f1 100644
fb6d68
--- a/util.c
fb6d68
+++ b/util.c
fb6d68
@@ -2798,6 +2798,9 @@ Perl_atfork_lock(void)
fb6d68
    dVAR;
fb6d68
 #if defined(USE_ITHREADS)
fb6d68
     /* locks must be held in locking order (if any) */
fb6d68
+#  ifdef USE_PERLIO
fb6d68
+    MUTEX_LOCK(&PL_perlio_mutex);
fb6d68
+#  endif
fb6d68
 #  ifdef MYMALLOC
fb6d68
     MUTEX_LOCK(&PL_malloc_mutex);
fb6d68
 #  endif
fb6d68
@@ -2812,6 +2815,9 @@ Perl_atfork_unlock(void)
fb6d68
     dVAR;
fb6d68
 #if defined(USE_ITHREADS)
fb6d68
     /* locks must be released in same order as in atfork_lock() */
fb6d68
+#  ifdef USE_PERLIO
fb6d68
+    MUTEX_UNLOCK(&PL_perlio_mutex);
fb6d68
+#  endif
fb6d68
 #  ifdef MYMALLOC
fb6d68
     MUTEX_UNLOCK(&PL_malloc_mutex);
fb6d68
 #  endif
fb6d68
-- 
fb6d68
1.8.1.4
fb6d68