Process connector can now also detect coredumping events. Main aim of patch is get notified at start of coredumping, instead of having to wait for it to finish and then being notified through EXIT event. Could be used for instance by process-managers that want to get notified as soon as possible about process failures, and not necessarily beeing notified after coredump, which could be in the order of minutes depending on size of coredump, piping and so on.
Showing the changes to include/uapi/linux (1 of 4 files). Show all
Unified · Split
| @@ -56,7 +56,9 @@ struct proc_event { · 55 unmodified lines | ||
| 56 | 56 | PROC_EVENT_PTRACE = 0x00000100, |
| 57 | 57 | PROC_EVENT_COMM = 0x00000200, |
| 58 | 58 | /* "next" should be 0x00000400 */ |
| 59 | − /* "last" is the last process event: exit */ | |
| 59 | + /* "last" is the last process event: exit, | |
| 60 | + * while "next to last" is coredumping event */ | |
| 61 | + PROC_EVENT_COREDUMP = 0x40000000, | |
| 60 | 62 | PROC_EVENT_EXIT = 0x80000000 |
| 61 | 63 | } what; |
| 62 | 64 | __u32 cpu; |
| @@ -110,11 +112,17 @@ struct proc_event { · 47 unmodified lines | ||
| 110 | 112 | char comm[16]; |
| 111 | 113 | } comm; |
| 112 | 114 | |
| 115 | + struct coredump_proc_event { | |
| 116 | + __kernel_pid_t process_pid; | |
| 117 | + __kernel_pid_t process_tgid; | |
| 118 | + } coredump; | |
| 119 | + | |
| 113 | 120 | struct exit_proc_event { |
| 114 | 121 | __kernel_pid_t process_pid; |
| 115 | 122 | __kernel_pid_t process_tgid; |
| 116 | 123 | __u32 exit_code, exit_signal; |
| 117 | 124 | } exit; |
| 125 | + | |
| 118 | 126 | } event_data; |
| 119 | 127 | }; |
| 120 | 128 | |