[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c49f552e34784e8dbb40a43015bed642@AcuMS.aculab.com>
Date: Thu, 1 Nov 2018 11:33:29 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Daniel Colascione' <dancol@...gle.com>,
Tycho Andersen <tycho@...ho.ws>
CC: linux-kernel <linux-kernel@...r.kernel.org>,
Tim Murray <timmurray@...gle.com>,
Joel Fernandes <joelaf@...gle.com>,
"Suren Baghdasaryan" <surenb@...gle.com>,
Aleksa Sarai <cyphar@...har.com>,
"Christian Brauner" <christian.brauner@...onical.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Kees Cook <keescook@...omium.org>,
Oleg Nesterov <oleg@...hat.com>
Subject: RE: [PATCH v3] Implement /proc/pid/kill
From: Daniel Colascione
> Sent: 31 October 2018 19:33
...
> You can't do it today with kill. The idea that keeping a open file
> descriptor to a /proc/pid or a file within it prevents PID reuse is
> widespread, but incorrect.
Is there a real good reason why that shouldn't be the case?
ie Holding a reference on the 'struct pid' being enough to stop reuse.
A patch to do that would be more generally useful.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists