ess and/or thread ID.
Add parent pid and tgid to coredump and exit process connectors event
data.
Signed-off-by: Stefan Strogin
Acked-by: Evgeniy Polyakov
---
drivers/connector/cn_proc.c | 4
include/uapi/linux/cn_proc.h | 4
2 files changed, 8 insertions(+)
diff --git a/drivers
to me.
>
> /Jesper
>
> ________
> Från: Stefan Strogin
> Skickat: den 2 april 2018 17:18
> Till: David Miller
> Kopia: z...@ioremap.net; netdev@vger.kernel.org;
> linux-ker...@vger.kernel.org; xe-linux-exter...@cisco.com;
> jdere...@hotma
Hi Evgeniy,
On 09/04/18 02:49, Evgeniy Polyakov wrote:
> Hi everyone
>
> Sorry for that late reply
>
> 01.03.2018, 21:58, "Stefan Strogin" :
>> So I was thinking to add these two fields to union event_data:
>> task->signal->group_exit_code
>> t
t, because comm_proc_event (also a member of event_data) is
of bigger size than the changed structures.
If I'm wrong, could you please explain what exactly will the change
break in UAPI?
On 30/03/18 19:59, David Miller wrote:
> From: Stefan Strogin
> Date: Thu, 29 Mar 2018 17:12:47 +0300
>
ess and/or thread ID.
Add parent pid and tgid to coredump and exit process connectors event
data.
Signed-off-by: Stefan Strogin
---
drivers/connector/cn_proc.c | 4
include/uapi/linux/cn_proc.h | 4
2 files changed, 8 insertions(+)
diff --git a/drivers/connector/cn_proc.c b/drivers
gt;group_exit_code
task->signal->flags
This won't increase size of struct proc_event (because of comm_proc_event)
and shouldn't break backward compatibility for the user-space. But it will
add some useful information about what caused the process death.
What do you think, is it an acce
