From: ebiederm@xmission.com (Eric W. Biederman)
To: Andy Lutomirski <luto@amacapital.net>
Cc: David Herrmann <dh.herrmann@gmail.com>,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
systemd Mailing List <systemd-devel@lists.freedesktop.org>,
criu@openvz.org, Pavel Emelyanov <xemul@parallels.com>,
Cyrill Gorcunov <gorcunov@openvz.org>
Subject: Re: [RFC PATCH] proc, pidns: Add highpid
Date: Fri, 28 Nov 2014 21:34:09 -0600 [thread overview]
Message-ID: <87mw7aof2m.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <b0f6c4df0e8ef8afcc7b786edecb4be8c752941e.1417215468.git.luto@amacapital.net> (Andy Lutomirski's message of "Fri, 28 Nov 2014 15:05:01 -0800")
Andy Lutomirski <luto@amacapital.net> writes:
> Pid reuse is common, which means that it's difficult or impossible
> to read information about a pid from /proc without races.
Sigh.
What we need are not race free pids, but a file descriptor based process
management api. Possibly one that starts by handing you a proc
directory.
Which probably means that we need a proc file we can write to and send
signals to a process, and another proc file we can select on and wait
for the process to exit.
Making pids bigger just looks like bandaid.
Remember evovle things in the direction of an object capability system
things wind up being more maintainable.
Eric
next prev parent reply other threads:[~2014-11-29 3:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 23:05 Andy Lutomirski
2014-11-28 23:06 ` Andy Lutomirski
2014-11-29 3:34 ` Eric W. Biederman [this message]
2014-11-29 15:32 ` Andy Lutomirski
2014-11-29 4:23 ` Greg KH
2014-11-29 15:19 ` Andy Lutomirski
2014-11-29 16:06 ` Cyrill Gorcunov
2014-11-30 8:47 ` Florian Weimer
2014-11-30 22:08 ` Andy Lutomirski
2014-12-01 6:47 ` Florian Weimer
2014-12-01 12:33 ` Pavel Emelyanov
2014-11-30 16:45 ` David Herrmann
2014-11-30 22:05 ` Andy Lutomirski
2014-12-01 7:03 ` Konstantin Khlebnikov
2014-12-01 16:21 ` Andy Lutomirski
2014-12-01 16:39 ` Konstantin Khlebnikov
2014-12-01 16:48 ` Andy Lutomirski
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=87mw7aof2m.fsf@x220.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=criu@openvz.org \
--cc=dh.herrmann@gmail.com \
--cc=gorcunov@openvz.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=systemd-devel@lists.freedesktop.org \
--cc=xemul@parallels.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
Powered by JetHome