Bug 1311166 - bld_eprog() signal leak
bld_eprog() signal leak
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: zsh (Show other bugs)
Unspecified Unspecified
urgent Severity high
: rc
: ---
Assigned To: Kamil Dudka
Branislav Náter
: Patch, ZStream
Depends On: 1198671
Blocks: 1316945
  Show dependency treegraph
Reported: 2016-02-23 09:41 EST by Filip Krska
Modified: 2016-09-14 09:12 EDT (History)
6 users (show)

See Also:
Fixed In Version: zsh-4.3.11-6.el6
Doc Type: Bug Fix
Doc Text:
Previously, if the zsh process received a signal during the execution of a memory allocation function and the signal handler attempted to allocate or free memory, zsh entered a deadlock and became unresponsive. With this update, signal handlers are no longer enabled while handling the global state of zsh or while using the heap memory allocator, which ensures that the described deadlock no longer occurs.
Story Points: ---
Clone Of:
: 1311172 1316945 (view as bug list)
Last Closed: 2016-09-14 09:12:28 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
[PATCH] signal-handling related fixes collected from upstream (9.88 KB, patch)
2016-03-01 12:25 EST, Kamil Dudka
kdudka: review?
Details | Diff

  None (edit)
Description Filip Krska 2016-02-23 09:41:43 EST
Description of problem:

zhandler() - free() deadlock in bld_eprog():

(gdb) bt
#0  __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97
#1  0x000000333827cdc0 in _L_lock_5199 () from /lib64/libc-2.12.so
#2  0x000000333827871b in _int_free (av=0x333858fe80, p=0x24b9a10, have_lock=0) at malloc.c:4963
#3  0x000000000044362d in freejob (jn=0x249a560, deleting=1) at jobs.c:1103
#4  0x000000000044486d in printjob (jn=0x249a560, lng=0, synch=0) at jobs.c:1066
#5  0x00000000004472da in update_job (jn=0x249a560) at jobs.c:508
#6  0x0000000000473bcb in wait_for_processes () at signals.c:502
#7  0x0000000000474495 in zhandler (sig=17) at signals.c:584
#8  <signal handler called>
#9  0x0000003338278443 in _int_free (av=0x333858fe80, p=0x24baf20, have_lock=0) at malloc.c:4973
#10 0x0000000000465a47 in bld_eprog () at parse.c:413
#11 0x000000000040f134 in bin_test (name=0x7f49c1ad7120 "[", argv=0x7f49c1ad7528, ops=<value optimized out>, 
    func=<value optimized out>) at builtin.c:5851

Version-Release number of selected component (if applicable):


How reproducible:

Happened in production, not reproduced in test environment so far.

Steps to Reproduce:

Actual results:

zsh deadlocks in futex-wait state.

Expected results:

zsh doesn't deadlock

Additional info:

zsh-5.0.2-18.el7 will suffer as well. Fixed in upstream zsh-5.2, backport patch proposal:

diff -up zsh-4.3.11/Src/parse.c.bld_eprog_sigleak zsh-4.3.11/Src/parse.c
--- zsh-4.3.11/Src/parse.c.bld_eprog_sigleak	2016-02-23 15:34:15.063441138 +0100
+++ zsh-4.3.11/Src/parse.c	2016-02-23 15:35:04.369447251 +0100
@@ -391,6 +391,8 @@ bld_eprog(void)
     Eprog ret;
     int l;
+    queue_signals();
     ret = (Eprog) zhalloc(sizeof(*ret));
@@ -413,6 +415,8 @@ bld_eprog(void)
     zfree(ecbuf, eclen);
     ecbuf = NULL;
+    unqueue_signals();
     return ret;

Please, consider re-initiating talks about calling free() (non signal safe function i.e. not supposed to be called from signal handlers) from zhandler() and re-scan of rhel6/7/upstream zsh code for any other possible signal leaks again.
Comment 2 Kamil Dudka 2016-03-01 12:25 EST
Created attachment 1132001 [details]
[PATCH] signal-handling related fixes collected from upstream

I am attaching my proposal of a conservative backport of the signal-handling upstream patches for RHEL-6.  A review would be much appreciated!
Comment 10 Marcel Kolaja 2016-09-14 09:12:28 EDT
The fix for this bug has been delivered in RHEL 6.7.z and this component has not been updated in RHEL 6.8. RHEL 6.8 contains the fix from RHEL 6.7.z. Therefore, this bug has been closed as CURRENTRELEASE.

Note You need to log in before you can comment on or make changes to this bug.