The patch titled
ptrace: make pid of child process available for PTRACE_EVENT_VFORK_DONE
has been added to the -mm tree. Its filename is
ptrace-make-pid-of-child-process-available-for.patch
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: ptrace: make pid of child process available for PTRACE_EVENT_VFORK_DONE
From: Chuck Ebbert <76306.1226@xxxxxxxxxxxxxx>
When delivering PTRACE_EVENT_VFORK_DONE, provide pid of the child process
when tracer calls ptrace(PTRACE_GETEVENTMSG). This is already
(accidentally) available when the tracer is tracing VFORK in addition to
VFORK_DONE.
Signed-off-by: Chuck Ebbert <76306.1226@xxxxxxxxxxxxxx>
Cc: Daniel Jacobowitz <dan@xxxxxxxxxx>
Cc: Albert Cahalan <acahalan@xxxxxxxxx>
Cc: Roland McGrath <roland@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
kernel/fork.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff -puN kernel/fork.c~ptrace-make-pid-of-child-process-available-for kernel/fork.c
--- a/kernel/fork.c~ptrace-make-pid-of-child-process-available-for
+++ a/kernel/fork.c
@@ -1387,8 +1387,10 @@ long do_fork(unsigned long clone_flags,
if (clone_flags & CLONE_VFORK) {
wait_for_completion(&vfork);
- if (unlikely (current->ptrace & PT_TRACE_VFORK_DONE))
+ if (unlikely (current->ptrace & PT_TRACE_VFORK_DONE)) {
+ current->ptrace_message = nr;
ptrace_notify ((PTRACE_EVENT_VFORK_DONE << 8) | SIGTRAP);
+ }
}
} else {
free_pid(pid);
_
Patches currently in -mm which might be from 76306.1226@xxxxxxxxxxxxxx are
ptrace-make-pid-of-child-process-available-for.patch
i386-print-stack-size-in-oops-messages.patch
sleazy-fpu-feature-i386-support.patch
i386-early-fault-handler.patch
i386-fix-recursive-faults-during-oops-when-current.patch
i386-show_registers-try-harder-to-print-failing.patch
spinlock_debug-dont-recompute-jiffies_per_loop.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
