Red Hat Bugzilla – Bug 233540
utrace: wait does not report immediately after PTRACE_ATTACH of process already in job control stop
Last modified: 2007-11-30 17:07:42 EST
+++ This bug was initially created as a clone of Bug #232837 +++
The frysk test suite now has a good regression test for this issue, which I've
fixed in the Fedora kernel. The behavior is a regression from RHEL4 and all
This bugzilla has Keywords: Regression.
Since no regressions are allowed between releases,
it is also being proposed as a blocker for this release.
Please resolve ASAP.
This request was evaluated by Red Hat Kernel Team for inclusion in a Red
Hat Enterprise Linux maintenance release, and has moved to bugzilla
Which testcase should be used to verify this bug? This is the only difference
I'm seeing in running the test suite that comes with frysk. Is the stopkills
test case the one I should be looking at for this bug?
[root@test183 tests]# diff out.2.6.18-*
< PASS: frysk4330/stopkills
> FAIL: frysk4330/stopkills
[root@test183 tests]# echo diff out.2.6.18-*
diff out.2.6.18-43.el5 out.2.6.18-8.el5
the failure mode according to strace is the ptrace(PTRACE_DETACH,...) call is
failing with a -ESRCH (No such process), but I'm not sure if that applies here.
nevermind... looks like the testcase I mentioned in comment 7 is for bz235545
which is also fixed. :). I found the testcase in Bug #232837 and I can confirm
it is fixed with the -43 kernel.
*** Bug 289411 has been marked as a duplicate of this bug. ***
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.