From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from zeniv.linux.org.uk ([195.92.253.2]:51590 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725888AbeKSNJp (ORCPT ); Mon, 19 Nov 2018 08:09:45 -0500 Date: Mon, 19 Nov 2018 02:47:04 +0000 From: Al Viro To: Andy Lutomirski Cc: Daniel Colascione , Randy Dunlap , Christian Brauner , "Eric W. Biederman" , LKML , "Serge E. Hallyn" , Jann Horn , Andrew Morton , Oleg Nesterov , Aleksa Sarai , Linux FS Devel , Linux API , Tim Murray , Kees Cook , Jan Engelhardt Subject: Re: [PATCH] proc: allow killing processes via file descriptors Message-ID: <20181119024704.GK32577@ZenIV.linux.org.uk> References: <20181118111751.6142-1-christian@brauner.io> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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?