Bug 1075635
| Summary: | ksh exit produces "Interrupt (core dumped)" | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Carlos Santos <casantos> | ||||||
| Component: | ksh | Assignee: | Michal Hlavinka <mhlavink> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Martin Kyral <mkyral> | ||||||
| Severity: | low | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 6.5 | CC: | fkrska, fleite, jraju, mkyral, ovasik, rhayden.public | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | 6.6 | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | ksh-20120801-16.el6 | Doc Type: | Bug Fix | ||||||
| Doc Text: |
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.
|
Story Points: | --- | ||||||
| Clone Of: | |||||||||
| : | 1085385 (view as bug list) | Environment: | |||||||
| Last Closed: | 2014-10-14 07:04:50 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
reproducible 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
Created attachment 884059 [details]
backported upstream fix
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.