Bug 742244 - ksh script never comes back
Summary: ksh script never comes back
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ksh
Version: 6.1
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: 6.2
Assignee: Michal Hlavinka
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks: 743302
TreeView+ depends on / blocked
 
Reported: 2011-09-29 13:46 UTC by Marko Karg
Modified: 2018-11-26 18:35 UTC (History)
4 users (show)

Fixed In Version: ksh-20100621-10.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 16:25:10 UTC
Target Upstream Version:


Attachments (Terms of Use)
strace of the script on 64bit (8.81 KB, application/octet-stream)
2011-09-29 13:46 UTC, Marko Karg
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1647 0 normal SHIPPED_LIVE ksh bug fix update 2011-12-06 00:50:33 UTC

Description Marko Karg 2011-09-29 13:46:22 UTC
Created attachment 525570 [details]
strace of the script on 64bit

Description of problem:

On RHEL 6.1 64bit the following ksh never comes back:

#!/bin/ksh
f_cmd () {
	CMD="$1"
	OUT="$(eval "$CMD" 2>&1)"
	echo "$OUT"
}
f_cmd "dd if=/dev/zero bs=128001 count=1 | cat | cat >/dev/null"

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

ksh-20100621-6.el6.x86_64

How reproducible:

always

Steps to Reproduce:
1. run the script from above on a 64bit RHEL 6.1 machine
  
Actual results:

The script never exits

Expected results:

Script should exit after executing the commands

Additional info:

The problem only occurs on 64bit architecture, not on 32bit. Also, current fedora 64bit does not show the problem.

Comment 10 errata-xmlrpc 2011-12-06 16:25:10 UTC
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-2011-1647.html


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