Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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 1117132[details]
backtrace
Description of problem:
Script containing ulimit -v 100000 causes zsh to segfault:
[0 root@qeos-21 test]# cat segv.sh
ulimit -v 100000
ls
[0 root@qeos-21 test]# zsh segv.sh
Segmentation fault (core dumped)
[0 root@qeos-21 test]# echo $?
139
By further examination I found out, that the problem is bad handling of the memory allocation if the memory limit set by ulimit -v is too strict.
ksh and bash are ok with this particular value. When I set it really low (ulimit -v 100), the script gets killed by SIGKILL which is better than SIGSEGV.
Version-Release number of selected component (if applicable):
zsh-4.3.11-4.el6_7.1
How reproducible:
always
Steps to Reproduce:
1. see description
2.
3.
Actual results:
[0 root@qeos-21 test]# zsh segv.sh
Segmentation fault (core dumped)
[0 root@qeos-21 test]# echo $?
139
Expected results:
[0 root@qeos-21 test]# zsh segv.sh
Killed
[0 root@qeos-21 test]# echo $?
137
Additional info:
It may be necessary to use lower ulimit -v value to reproduce.
Thank you for reporting the bug. From the backtrace it is clear that it crashes due to infinite recursion and stack overflow. zalloc() fails to allocate memory, so it wants to print a fatal error message and exit. The problem is that zerr(), which is used to print the error message, transitively calls back to zalloc().
In order to prevent the stack overflow, we need to:
1. either make zalloc() not call zerr(),
2. make zerr() not transitively call back to zalloc(), or
3. introduce a flag that will break the recursion in cases like this.
Created attachment 1118021[details]
proof-of-concept reproducer
I have attached a universal reproducer script. It is not completely reliable because dynamic linker and pthread run-time may run out of memory sooner than zsh itself in some cases. Nevertheless, I am able to trigger the infinite recursion with upstream git HEAD if I create a statically linked executable.
Red Hat Enterprise Linux 6 transitioned to the Production 3 Phase on May 10, 2017. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
http://redhat.com/rhel/lifecycle
This issue does not appear to meet the inclusion criteria for the Production Phase 3 and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:
https://access.redhat.com
Created attachment 1117132 [details] backtrace Description of problem: Script containing ulimit -v 100000 causes zsh to segfault: [0 root@qeos-21 test]# cat segv.sh ulimit -v 100000 ls [0 root@qeos-21 test]# zsh segv.sh Segmentation fault (core dumped) [0 root@qeos-21 test]# echo $? 139 By further examination I found out, that the problem is bad handling of the memory allocation if the memory limit set by ulimit -v is too strict. ksh and bash are ok with this particular value. When I set it really low (ulimit -v 100), the script gets killed by SIGKILL which is better than SIGSEGV. Version-Release number of selected component (if applicable): zsh-4.3.11-4.el6_7.1 How reproducible: always Steps to Reproduce: 1. see description 2. 3. Actual results: [0 root@qeos-21 test]# zsh segv.sh Segmentation fault (core dumped) [0 root@qeos-21 test]# echo $? 139 Expected results: [0 root@qeos-21 test]# zsh segv.sh Killed [0 root@qeos-21 test]# echo $? 137 Additional info: It may be necessary to use lower ulimit -v value to reproduce.