Re: [RFC PATCH] set TASK_TRACED before arch_ptrace code to fix a race

From: Luming Yu
Date: Wed May 28 2008 - 05:14:39 EST


Some correction about the test case hang, the ps output should looks
like the following:
13925 S+ strace -f ./test1
13926 S+ ./test1
13927 T+ /bin/bash ./test2

I'm trying upstream kdump to get more detailed data for help analysis
the scenario..
But unfortunately upstream kernel just hang when I echo c to
sysrq-trigger. Downgrade the kernel to 2.6.22, 'echo c' doesn't
hang, but I just got "zero" dump file...
Will try F9 later... But from the symptom shouldn't we ask this
question: why process 13927 can't wake up? Roland, please confirm
if ptrace_untrace is the only way to get Traced process wake up? Back
up to caller of ptrace_untrace, maybe we can find out why my RFC patch
happen to fix the problem... Any suggestions are welcome!
--Luming
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/