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.
Previously, ksh did not mask the exit code and sometimes returned too high number that could be later interpreted as a termination by a signal. When ksh started from a su utility exited with high number exit code, su incorrectly reported that it was interrupted and core dumped. Ksh was updated to mask the exit code when terminating to prevent a confusion of parent process. With this update su utility no longer incorrectly thinks ksh was terminated by a signal.
Created attachment 873570[details]
Do not re-send signal on termination, just set signal number +128 as exit code.
Description of problem:
A unix user is configured with login shell as ksh. Every time if Ctrl+C is pressed after login and after that "exit" command is executed "Interrupt (core dumped)" message is produced. This is a regression introduced in ksh-20100621-19.el6_4.4. If you downgrade ksh to ksh-20120801-10.el6 you will observer that the problem does not happen.
--- With ksh-20120801-10.el6_5.3.x86_64 ---
[root@ibm-x3550-4 kshuser]# strace -f -ff -o /tmp/kshuser.20120801 su - kshuser
$ <--- ^C pressed
$ <--- ^D pressed
Interrupt (core dumped)
[root@ibm-x3550-4 kshuser]#
---
--- With ksh-20120801-10.el6_5.3.x86_64 ---
[root@ibm-x3550-4 tmp]# strace -f -ff -o /tmp/kshuser.20100621 su - kshuser
$ <--- ^C pressed
$ <--- ^D pressed
[root@ibm-x3550-4 tmp]#
---
Version-Release number of selected component (if applicable):
ksh-20120801-10.el6_5.3
How reproducible:
Always
Steps to Reproduce:
1. Set a user with /bin/ksh as shell, "kshuser"
2. Run "su - kshuser"
3. At the ksh prompt hit Control-C followed by Control-D
Actual results:
The "su" utility shows the message "Interrupt (core dumped)".
Expected results:
Only the exit code should be set.
Additional info:
The cause of the problem is that the ^C generates an INT signal that should be cleared by ksh before exitting but is sesent on termination. Therefore "su" infers that the user shell was interrupted and shows the corresponding message "Interrupt (core dumped)".
The problam can be avoided using the attached patch. I'm not sure if it is the best approach, however.
Comment on attachment 873570[details]
Do not re-send signal on termination, just set signal number +128 as exit code.
causes regressions in upstream test suit
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2014-1381.html
Created attachment 873570 [details] Do not re-send signal on termination, just set signal number +128 as exit code. Description of problem: A unix user is configured with login shell as ksh. Every time if Ctrl+C is pressed after login and after that "exit" command is executed "Interrupt (core dumped)" message is produced. This is a regression introduced in ksh-20100621-19.el6_4.4. If you downgrade ksh to ksh-20120801-10.el6 you will observer that the problem does not happen. --- With ksh-20120801-10.el6_5.3.x86_64 --- [root@ibm-x3550-4 kshuser]# strace -f -ff -o /tmp/kshuser.20120801 su - kshuser $ <--- ^C pressed $ <--- ^D pressed Interrupt (core dumped) [root@ibm-x3550-4 kshuser]# --- --- With ksh-20120801-10.el6_5.3.x86_64 --- [root@ibm-x3550-4 tmp]# strace -f -ff -o /tmp/kshuser.20100621 su - kshuser $ <--- ^C pressed $ <--- ^D pressed [root@ibm-x3550-4 tmp]# --- Version-Release number of selected component (if applicable): ksh-20120801-10.el6_5.3 How reproducible: Always Steps to Reproduce: 1. Set a user with /bin/ksh as shell, "kshuser" 2. Run "su - kshuser" 3. At the ksh prompt hit Control-C followed by Control-D Actual results: The "su" utility shows the message "Interrupt (core dumped)". Expected results: Only the exit code should be set. Additional info: The cause of the problem is that the ^C generates an INT signal that should be cleared by ksh before exitting but is sesent on termination. Therefore "su" infers that the user shell was interrupted and shows the corresponding message "Interrupt (core dumped)". The problam can be avoided using the attached patch. I'm not sure if it is the best approach, however.