1TRACEHOOK_REPORT_CLO(9) Kernel Internals TRACEHOOK_REPORT_CLO(9)
2
3
4
6 tracehook_report_clone - in parent, new child is about to start running
7
9 void tracehook_report_clone(struct pt_regs * regs,
10 unsigned long clone_flags, pid_t pid,
11 struct task_struct * child);
12
14 regs
15 parent's user register state
16
17 clone_flags
18 flags from parent's system call
19
20 pid
21 new child's PID in the parent's namespace
22
23 child
24 new child task
25
27 Called after a child is set up, but before it has been started running.
28 This is not a good place to block, because the child has not started
29 yet. Suspend the child here if desired, and then block in
30 tracehook_report_clone_complete. This must prevent the child from
31 self-reaping if tracehook_report_clone_complete uses the child pointer;
32 otherwise it might have died and been released by the time
33 tracehook_report_clone_complete is called.
34
35 Called with no locks held, but the child cannot run until this returns.
36
37
38
39Kernel Hackers Manual 2.6. November 2011 TRACEHOOK_REPORT_CLO(9)