Bug 143073 - traced process cannot be killed
traced process cannot be killed
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
4.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Roland McGrath
Brian Brock
:
Depends On:
Blocks: 137160 139815 145334 147461
  Show dependency treegraph
 
Reported: 2004-12-16 06:46 EST by Yoav Zach
Modified: 2010-10-21 22:44 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-06-08 11:13:12 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)
test case to demonstrate the problem (1.28 KB, text/plain)
2004-12-16 06:46 EST, Yoav Zach
no flags Details
machine-independent version of the test case (958 bytes, text/plain)
2004-12-24 17:42 EST, Roland McGrath
no flags Details
three-thread version of the test case (1.21 KB, text/plain)
2004-12-24 19:01 EST, Roland McGrath
no flags Details

  None (edit)
Description Yoav Zach 2004-12-16 06:46:30 EST
Description of problem:
when a process is traced it cannot be killed by sending it a signal

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

How reproducible:
consistently

Steps to Reproduce:
1.Build the attaced file by doing "gcc -o suspend suspend_thread.c -lpthread -
D_REENTRANT"

2. run ./suspend
3.
  
Actual results:
On EL4 pre-rc1:

[~/tests/64/thread_suspension]./suspend_thread 
Thread 13742720(7344) is started.
thread 7344 is stopped
(the application is hanged and cannot be killed)



Expected results:
On EL3 U3:
[~/tests/64/thread_suspension]./suspend 
Thread 13662416(4942) is started.
thread 4942 is stopped
Segmentation fault



Additional info: this is the rootcause of bugzilla #139815
Comment 1 Yoav Zach 2004-12-16 06:46:30 EST
Created attachment 108684 [details]
test case to demonstrate the problem
Comment 3 Roland McGrath 2004-12-24 17:42:58 EST
Created attachment 109114 [details]
machine-independent version of the test case

This is a modified version of the given test case, that can be compiled on any
architecture and demonstrates the problem on x86 using the current upstream
kernel.  This version can also take a signal number argument on its command
line.
Using this with non-coredump signals demonstrates that there is no problem
except in the coredump case.
Comment 4 Roland McGrath 2004-12-24 19:01:40 EST
Created attachment 109116 [details]
three-thread version of the test case

This version of the test case has three threads, so that the ptracer, the
ptracee, and the thread causing the core dump and all separate.  Some
approaches to the fix work for the prior test case but not for this one.
Comment 9 Tim Powers 2005-06-08 11:13:12 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2005-420.html

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