From: David Laight <David.Laight@ACULAB.COM>
To: 'Daniel Colascione' <dancol@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "timmurray@google.com" <timmurray@google.com>,
"joelaf@google.com" <joelaf@google.com>
Subject: RE: [RFC PATCH] Minimal non-child process exit notification support
Date: Wed, 31 Oct 2018 12:27:12 +0000 [thread overview]
Message-ID: <4beaaae77bea4cc5b4cc15504331c9a9@AcuMS.aculab.com> (raw)
In-Reply-To: <20181029175322.189042-1-dancol@google.com>
From: Daniel Colascione
> Sent: 29 October 2018 17:53
>
> This patch adds a new file under /proc/pid, /proc/pid/exithand.
> Attempting to read from an exithand file will block until the
> corresponding process exits, at which point the read will successfully
> complete with EOF. The file descriptor supports both blocking
> operations and poll(2). It's intended to be a minimal interface for
> allowing a program to wait for the exit of a process that is not one
> of its children.
Why do you need an extra file?
It ought to be possible to use poll() to wait for POLLERR having set
'events' to zero on any of the nodes in /proc/pid - or even on
the directory itself.
Indeed, to avoid killing the wrong process you need to have opened
some node of /proc/pid/* (maybe cmdline) before sending the kill
signal.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2018-10-31 12:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 17:53 [RFC PATCH] Minimal non-child process exit notification support Daniel Colascione
2018-10-29 19:22 ` [RFC PATCH v2] " Daniel Colascione
2018-11-01 7:00 ` Aleksa Sarai
2018-11-01 7:06 ` Aleksa Sarai
2018-11-01 9:58 ` Christian Brauner
2018-11-01 9:59 ` Daniel Colascione
2018-11-01 10:47 ` Aleksa Sarai
2018-11-01 11:32 ` Daniel Colascione
2018-10-29 19:45 ` [RFC PATCH] " Joel Fernandes
2018-10-29 19:47 ` Joel Fernandes
2018-10-29 20:01 ` Daniel Colascione
2018-10-30 3:06 ` Joel Fernandes
2018-10-30 8:59 ` Daniel Colascione
2018-10-30 22:24 ` Joel Fernandes
2018-10-31 12:27 ` David Laight [this message]
2018-10-31 12:56 ` Daniel Colascione
2018-10-31 14:25 ` David Laight
2018-10-31 14:41 ` Joel Fernandes
2018-10-31 14:43 ` Joel Fernandes
2018-10-31 14:48 ` Daniel Colascione
2018-10-31 16:53 ` Daniel Colascione
[not found] ` <175DDE5D-E738-4C35-B664-6AD8B9CF446D@amacapital.net>
2018-10-31 17:44 ` Daniel Colascione
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=4beaaae77bea4cc5b4cc15504331c9a9@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=dancol@google.com \
--cc=joelaf@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=timmurray@google.com \
/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).