[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181119024704.GK32577@ZenIV.linux.org.uk>
Date: Mon, 19 Nov 2018 02:47:04 +0000
From: Al Viro <viro@...IV.linux.org.uk>
To: Andy Lutomirski <luto@...nel.org>
Cc: Daniel Colascione <dancol@...gle.com>,
Randy Dunlap <rdunlap@...radead.org>,
Christian Brauner <christian@...uner.io>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
LKML <linux-kernel@...r.kernel.org>,
"Serge E. Hallyn" <serge@...lyn.com>, Jann Horn <jannh@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Oleg Nesterov <oleg@...hat.com>,
Aleksa Sarai <cyphar@...har.com>,
Linux FS Devel <linux-fsdevel@...r.kernel.org>,
Linux API <linux-api@...r.kernel.org>,
Tim Murray <timmurray@...gle.com>,
Kees Cook <keescook@...omium.org>,
Jan Engelhardt <jengelh@...i.de>
Subject: Re: [PATCH] proc: allow killing processes via file descriptors
On Sun, Nov 18, 2018 at 09:42:35AM -0800, Andy Lutomirski wrote:
> Now here's the kicker: if the "running program" calls execve(), it
> goes away. The fd gets some sort of notification that this happened
Type error, parser failed.
Define "fd", please. If it's a "file descriptor", thank you do playing,
you've lost. That's not going to work. If it's "opened file" (aka
"file description" in horrible POSIXese), who's going to get notifications
and what kind of exclusion are you going to use?
Powered by blists - more mailing lists