1TRACEHOOK_NOTIFY_JCT(9)        Kernel Internals        TRACEHOOK_NOTIFY_JCT(9)
2
3
4

NAME

6       tracehook_notify_jctl - report about job control stop/continue
7

SYNOPSIS

9       int tracehook_notify_jctl(int notify, int why);
10

ARGUMENTS

12       notify
13           zero, CLD_STOPPED or CLD_CONTINUED
14
15       why
16
17           CLD_STOPPED or CLD_CONTINUED
18

DESCRIPTION

20       This is called when we might call do_notify_parent_cldstop.
21
22       notify is zero if we would not ordinarily send a SIGCHLD, or is the
23       CLD_STOPPED or CLD_CONTINUED .si_code for SIGCHLD.
24
25       why is CLD_STOPPED when about to stop for job control; we are already
26       in TASK_STOPPED state, about to call schedule. It might also be that we
27       have just exited (check PF_EXITING), but need to report that a
28       group-wide stop is complete.
29
30       why is CLD_CONTINUED when waking up after job control stop and ready to
31       make a delayed notify report.
32
33       Return the CLD_* value for SIGCHLD, or zero to generate no signal.
34
35       Called with the siglock held.
36
37
38
39Kernel Hackers Manual 2.6.         June 2019           TRACEHOOK_NOTIFY_JCT(9)