From: Solar Designer <solar@openwall.com>
To: kernel-hardening@lists.openwall.com
Subject: race-free process signaling
Date: Mon, 6 May 2019 12:21:12 +0200 [thread overview]
Message-ID: <20190506102112.GA12668@openwall.com> (raw)
Hi,
I totally missed the recent work in this area (I'm not on LKML), and am
now wondering whether the solution that got in ("use /proc/<pid> fds as
stable handles on struct pid"):
https://lwn.net/Articles/773459/
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a9dce6679d736cb3d612af39bab9f31f8db66f9b
is better or worse than what I had proposed in 1999 and 2005 ("locking"
of pids for the caller's own visibility only):
https://marc.info/?l=linux-kernel&m=112784189115058
[Subject starts with "PID reuse safety for userspace apps", in case MARC
is ever gone and someone wants to look this up in another archive.
I proposed a lockpid syscall back then, but I'd use a mere prctl now.]
I still like my proposal much better - no dependency on procfs, much
simpler implementation - but perhaps I'm missing the context here.
Maybe I should have sent a patch back then. Oh well.
Alexander
next reply other threads:[~2019-05-06 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 10:21 Solar Designer [this message]
2019-05-06 10:45 ` race-free process signaling Jann Horn
2019-05-06 11:14 ` Christian Brauner
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=20190506102112.GA12668@openwall.com \
--to=solar@openwall.com \
--cc=kernel-hardening@lists.openwall.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.