Bug 456443 - ptrace: reparent-zombie testcase FAILs
ptrace: reparent-zombie testcase FAILs
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
4.7
All Linux
high Severity high
: rc
: ---
Assigned To: Vitaly Mayatskikh
Martin Jenner
:
Depends On:
Blocks: 461297
  Show dependency treegraph
 
Reported: 2008-07-23 14:00 EDT by Jan Kratochvil
Modified: 2009-05-19 11:43 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-05-19 11:43:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jan Kratochvil 2008-07-23 14:00:14 EDT
Description of problem:
The testcase program
http://sources.redhat.com/cgi-bin/cvsweb.cgi/~checkout~/tests/ptrace-tests/tests/reparent-zombie.c?cvsroot=systemtap
should PASS as on F-9 (utrace) kernels and (reportedly) upstream 2.6.26+.
(/proc/PID/status should not be left Zombie for parents with SIG_IGN SIGCHLD.)

Version-Release number of selected component (if applicable):
kernel-smp-2.6.9-78.EL.x86_64

How reproducible:
Always.

Steps to Reproduce:
wget -O reparent-zombie.c
http://sources.redhat.com/cgi-bin/cvsweb.cgi/~checkout~/tests/ptrace-tests/tests/reparent-zombie.c?cvsroot=systemtap;
gcc -o reparent-zombie reparent-zombie.c -Wall -ggdb2 -D_GNU_SOURCE -pthread;
./reparent-zombie; echo $?

Actual results:
24649 left in State:	Z (zombie)
1

Expected results:
0

Additional info:
It was reported by Roland at http://sourceware.org/systemtap/wiki/utrace/tests
as "fixed upstream after 2.6.26".

reparent-zombie-clone testcase also FAILs but only with the same result as this
Bug's testcase reparent-zombie with no kernel crash.  IMO kernel crash was the
reason for reparent-zombie-clone so it should get fixed along by this Bug.
Comment 1 Vitaly Mayatskikh 2008-07-30 09:52:11 EDT
The bug is not reproducible not only in upstream kernel (2.6.27-rc1), but in F-9
(2.6.25.11-97) and RHEL-5 (2.6.18-92.1.6) also. I see it only in RHEL-4. Are you
sure about 2.6.26+?
Comment 2 Jan Kratochvil 2008-07-30 11:42:51 EDT
(In reply to comment #1)
> The bug is not reproducible not only in upstream kernel (2.6.27-rc1), but in
> F-9 (2.6.25.11-97) and RHEL-5 (2.6.18-92.1.6) also. I see it only in RHEL-4.
> Are you sure about 2.6.26+?

(My comment #0)
> It was reported by Roland at http://sourceware.org/systemtap/wiki/utrace/tests
> as "fixed upstream after 2.6.26".

I do not see any contradictions.
I agree with you that:

RHEL-4 is broken - This Bug.
RHEL-5 is OK (expecting due to utrace - instead of upstream ptrace)
F-9 is OK (expecting due to utrace - instead of upstream ptrace)
upstream 2.6.27-rc1 is OK (as Roland said it is fixed upstream after 2.6.26)
My test on 2.6.25.6-55.vanilla.fc9.x86_64 shows it is broken (as expected)
Comment 3 RHEL Product and Program Management 2008-09-03 09:00:59 EDT
Updating PM score.
Comment 4 Linda Wang 2009-04-07 09:30:06 EDT
move back to ASSI, the patch posted need follow up after Roland's feedback.

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