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
Subject: Re: [PATCH RESEND] connector: add parent pid and tgid to coredump and exit events
Date: Tue, 01 May 2018 14:26:18 -0400 (EDT) [thread overview]
Message-ID: <20180501.142618.2096083030186678136.davem@davemloft.net> (raw)
In-Reply-To: <20180430220429.14788-1-sstrogin@cisco.com>
From: Stefan Strogin <sstrogin@cisco.com>
Date: Tue, 1 May 2018 01:04:29 +0300
> The intention is to get notified of process failures as soon
> as possible, before a possible core dumping (which could be very long)
> (e.g. in some process-manager). Coredump and exit process events
> are perfect for such use cases (see 2b5faa4c553f "connector: Added
> coredumping event to the process connector").
>
> The problem is that for now the process-manager cannot know the parent
> of a dying process using connectors. This could be useful if the
> process-manager should monitor for failures only children of certain
> parents, so we could filter the coredump and exit events by parent
> process and/or thread ID.
>
> Add parent pid and tgid to coredump and exit process connectors event
> data.
>
> Signed-off-by: Stefan Strogin <sstrogin@cisco.com>
> Acked-by: Evgeniy Polyakov <zbr@ioremap.net>
Applied to net-next, thank you.
prev parent reply other threads:[~2018-05-01 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 22:04 [PATCH RESEND] connector: add parent pid and tgid to coredump and exit events Stefan Strogin
2018-05-01 18:26 ` David Miller [this message]
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=20180501.142618.2096083030186678136.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jderehag@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.helsley@gmail.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).