Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Mon, 6 May 2019 12:21:12 +0200
From: Solar Designer <solar@...nwall.com>
To: kernel-hardening@...ts.openwall.com
Subject: race-free process signaling

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

Powered by blists - more mailing lists

Your e-mail address:

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.