Received: by 2002:ac0:98c7:0:0:0:0:0 with SMTP id g7-v6csp1315141imd; Thu, 1 Nov 2018 13:41:44 -0700 (PDT) X-Google-Smtp-Source: AJdET5cCVpJRbto8D7JNkCPF+Vu6CRCH8DXd8ToFFzgofOrvtLOGBQ1OlfGhvXIkeU3sT4gmouMB X-Received: by 2002:a17:902:1c3:: with SMTP id b61-v6mr9161398plb.65.1541104904225; Thu, 01 Nov 2018 13:41:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1541104904; cv=none; d=google.com; s=arc-20160816; b=PWuNf0TfluV6ROVGAqtXkFut5/p1TFXqoGKg2AjSsCChkxj5ogOF1joY7SyYPAzClv DYEKEbRiYG/xmy5VVnsBa4hNyYUZTiBUjidPcqIkYijADWKShf3/YncFhw0UTI3GUX84 VQ1HtMN+xxiXR9J5J84CapC1TosOG2iHQLAO/qtU9v16Xt1PwSUYGUjNMmSttUasDA1f iIPeZUNMQf9fgsoE22rbosryQcIMMAHQ1r4fHF7SQW0563A31QCR7t10qMX9+niatlyV 4FRkWl2UD9Y9ybf0tn0YrPnCvSMqY+sJ8S8P2/rL8YKCtt3wqjvMszYWHafUFxuEUijG 3uLA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=2hqnOlv6s9A6rZST2teucNVl1VbXK5yh0Jy3qZiXvO8=; b=oMsvoOF8ulUmHkJm/JsNc8w7GnzvD6dZ5R1/DDkwtDya7arWv02GaCtjHeeNMCgnI1 gIaqHo+RasR6Og/p3ZIPh57lD+yPzuBMxwS/VsKSj26HobKBzyFbl/9DN3Mv1JikXrSU /Nds8P9pv8iZjVUERSI0ieKBaSf/IZ0+BhfT5zOwP8HbnKp9/AZUny7DCp2gufEa6NzY u+CK/6hzIWfCxlpFoF9P3XVrnnC27y98ORI4zSzyTFOjv1WOqbWjQGAnw1Oh3g4PNJYI 2Uazhtt2mw0+M6vHneNvxuPi0b30nz6tOWN5dbQyrQhnZHx2NggIy+ny/Fp7DiyF6Qx/ ah2w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@joelfernandes.org header.s=google header.b=o7V4cNuj; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z31-v6si32458474plb.15.2018.11.01.13.41.26; Thu, 01 Nov 2018 13:41:44 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@joelfernandes.org header.s=google header.b=o7V4cNuj; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726094AbeKBFph (ORCPT + 99 others); Fri, 2 Nov 2018 01:45:37 -0400 Received: from mail-pg1-f193.google.com ([209.85.215.193]:34356 "EHLO mail-pg1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725963AbeKBFpg (ORCPT ); Fri, 2 Nov 2018 01:45:36 -0400 Received: by mail-pg1-f193.google.com with SMTP id k1-v6so8149279pgq.1 for ; Thu, 01 Nov 2018 13:41:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelfernandes.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=2hqnOlv6s9A6rZST2teucNVl1VbXK5yh0Jy3qZiXvO8=; b=o7V4cNuj1ITnzbmDWPLcR/3PaTnkz5Z7HbvITxoOwzTd5nc6NgUO6pu7X7zDLAR7bD gmM23JGZBcBHvVN4i53F6oYxYxWopXPog1nH9bTecx/AAwB2Yk+2evktG/E4CwQV6dxP /HRHe5herSNZcTzWxBv7meR9GLh3a7H+GW1Vs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=2hqnOlv6s9A6rZST2teucNVl1VbXK5yh0Jy3qZiXvO8=; b=dElOC+ST9V89H5h9KAjuUni5giy8gBKNE+FMR4qqNWi5OQxFP9VBKFmHfeg/R7Yc5/ BBu93lj1k3m4XK75R4uX4cElFDB7mSj71PTyA4QdnOJrL9x3rnn9TTkBq3obZuZeDoDp 7PMLCTbVAuHufmICDLMhrO4QpQW8rMXVcFq9swgFoq9zXxbwdIcssDloZpRpPrz8eLiz 7SbEuZ8soHBCZ2feAsPoTpC3NSZR/LYfTI62Jn+Nzaa808d3SI0LwwSZ1aMlyXxsVBlb GRWl25XvtEJLJmJQQzEKd7O5HYnUvAwL2ZJ7YI+ifWTII+g84jg+gMf478qjLqPZ5v/Z ljbw== X-Gm-Message-State: AGRZ1gIdamaR4smyaaWhpdXcYmCwPIb2JcBHD0h/DvfXnSDjFjZkTnKm dIi4EgmL9j/i68GIrAfpQozqkw== X-Received: by 2002:a63:9dca:: with SMTP id i193-v6mr7905127pgd.98.1541104861770; Thu, 01 Nov 2018 13:41:01 -0700 (PDT) Received: from localhost ([2620:0:1000:1601:3aef:314f:b9ea:889f]) by smtp.gmail.com with ESMTPSA id m20-v6sm38735079pfj.171.2018.11.01.13.40.59 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 01 Nov 2018 13:41:00 -0700 (PDT) Date: Thu, 1 Nov 2018 13:40:59 -0700 From: Joel Fernandes To: Aleksa Sarai Cc: Christian Brauner , Daniel Colascione , Linux Kernel Mailing List , Tim Murray , Suren Baghdasaryan Subject: Re: [RFC PATCH] Implement /proc/pid/kill Message-ID: <20181101204059.GA102756@google.com> References: <20181030050012.u43lcvydy6nom3ul@yavin> <20181030204501.jnbe7dyqui47hd2x@yavin> <20181030214243.GB32621@google.com> <20181030222339.ud4wfp75tidowuo4@yavin> <20181030223343.GB105735@joelaf.mtv.corp.google.com> <20181031025655.yz7lfhswk7igb3ty@yavin> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 30, 2018 at 09:24:00PM -0700, Joel Fernandes wrote: > On Tue, Oct 30, 2018 at 7:56 PM, Aleksa Sarai wrote: > > On 2018-10-31, Christian Brauner wrote: > >> > I think Aleksa's larger point is that it's useful to treat processes > >> > as other file-descriptor-named, poll-able, wait-able resources. > >> > Consistency is important. A process is just another system resource, > >> > and like any other system resource, you should be open to hold a file > >> > descriptor to it and do things to that process via that file > >> > descriptor. The precise form of this process-handle FD is up for > >> > debate. The existing /proc/$PID directory FD is a good candidate for a > >> > process handle FD, since it does almost all of what's needed. But > >> > regardless of what form a process handle FD takes, we need it. I don't > >> > see a case for continuing to treat processes in a non-unixy, > >> > non-file-descriptor-based manner. > >> > >> That's what I'm proposing in the API for which I'm gathering feedback. > >> I have presented parts of this in various discussions at LSS Europe last week > >> and will be at LPC. > >> We don't want to rush an API like this though. It was tried before in > >> other forms > >> and these proposals didn't make it. > > > > :+1: on a well thought-out and generic proposal. As we've discussed > > elsewhere, this is an issue that really would be great to (finally) > > solve. > > Excited to see this and please count me in for discussions around this. thanks. > Just a quick question, is there a track planned at LPC for discussing this new proposal or topics around/related to the proposal? If not, should that be planned? - Joel