linux-kernel - Re: [PATCH RESEND] connector: add parent pid and tgid to coredump and exit events

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 01 May 2018 14:26:18 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     sstrogin@...co.com
Cc:     zbr@...emap.net, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org, xe-linux-external@...co.com,
        jderehag@...mail.com, matt.helsley@...il.com
Subject: Re: [PATCH RESEND] connector: add parent pid and tgid to coredump
 and exit events

From: Stefan Strogin <sstrogin@...co.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@...co.com>
> Acked-by: Evgeniy Polyakov <zbr@...emap.net>

Applied to net-next, thank you.