From: David Miller <davem@davemloft.net>
To: sstrogin@cisco.com
Cc: zbr@ioremap.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, xe-linux-external@cisco.com,
jderehag@hotmail.com, matt.helsley@gmail.com,
minipli@googlemail.com
Subject: Re: [PATCH] connector: add parent pid and tgid to coredump and exit events
Date: Fri, 30 Mar 2018 12:59:21 -0400 (EDT) [thread overview]
Message-ID: <20180330.125921.653839794312978457.davem@davemloft.net> (raw)
In-Reply-To: <20180329141247.20943-1-sstrogin@cisco.com>
From: Stefan Strogin <sstrogin@cisco.com>
Date: Thu, 29 Mar 2018 17:12:47 +0300
> diff --git a/include/uapi/linux/cn_proc.h b/include/uapi/linux/cn_proc.h
> index 68ff25414700..db210625cee8 100644
> --- a/include/uapi/linux/cn_proc.h
> +++ b/include/uapi/linux/cn_proc.h
> @@ -116,12 +116,16 @@ struct proc_event {
> struct coredump_proc_event {
> __kernel_pid_t process_pid;
> __kernel_pid_t process_tgid;
> + __kernel_pid_t parent_pid;
> + __kernel_pid_t parent_tgid;
> } coredump;
>
> struct exit_proc_event {
> __kernel_pid_t process_pid;
> __kernel_pid_t process_tgid;
> __u32 exit_code, exit_signal;
> + __kernel_pid_t parent_pid;
> + __kernel_pid_t parent_tgid;
> } exit;
>
> } event_data;
I don't think you can add these members without breaking UAPI.
next prev parent reply other threads:[~2018-03-30 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 14:12 [PATCH] connector: add parent pid and tgid to coredump and exit events Stefan Strogin
2018-03-30 16:59 ` David Miller [this message]
2018-04-02 15:18 ` Stefan Strogin
[not found] ` <DB6P190MB0389513E240BD8ECEE575DB4DDBB0@DB6P190MB0389.EURP190.PROD.OUTLOOK.COM>
2018-04-26 12:04 ` Stefan Strogin
2018-04-30 15:01 ` Evgeniy Polyakov
2018-04-30 15:17 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180330.125921.653839794312978457.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jderehag@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.helsley@gmail.com \
--cc=minipli@googlemail.com \
--cc=netdev@vger.kernel.org \
--cc=sstrogin@cisco.com \
--cc=xe-linux-external@cisco.com \
--cc=zbr@ioremap.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).