Received: by 2002:ac0:98c7:0:0:0:0:0 with SMTP id g7-v6csp5608252imd; Tue, 30 Oct 2018 22:12:10 -0700 (PDT) X-Google-Smtp-Source: AJdET5cnAxh436eSBA10UZWoAkiLxS3ZBZo6hhRi+ObcmSacEGaau+cFaMnWCrX4Iy4ggmN3pO96 X-Received: by 2002:a63:164d:: with SMTP id 13-v6mr1687031pgw.103.1540962730656; Tue, 30 Oct 2018 22:12:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1540962730; cv=none; d=google.com; s=arc-20160816; b=y2wcXn2IjMeHjeHijrjFa0KmgkCtSrEhFGzqscngfvqbR8oAiR0aiHBiC+glXB0WsL rRjZh/qYPZqHVTSdvL0NW7n6G1olID8bEMy+NVlvUIUkfod3AKnIcS6uaH/0Sv6IKDeG Axx2hdIOFJNtZuh8hcK85BWFqga5iGxN1o5veYqKEQoK77iUp3oE4132TGlfIiwOO/m5 JJ52rvMhX7AN9UAnQc/qaZqeOSQSAOodn0AQKJQoXlDXLiZ92Qo/TsDr9XwW8EMzN/5U n95SPK4+HQfvabtIajPhEwKdtJgttJjkB8/o3kYaLsWAw05lXr9J3cLKhsZtp4KwaNZO GcRQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:subject:mime-version:user-agent :message-id:in-reply-to:date:references:cc:to:from; bh=IUzqGxoRQtz0iEvQmJuWO0A3iu3goNvHWAU2MY/6POA=; b=c3TXr5tyTMpv3C507oK0CSUXfkPjB1AkCJ4colzWBtW4Xe8bTwm9+lkAagn/VbxZ69 j4VfUUzQMYnAdSITPqI1hmwFKCj2/6qNrCL24INYFxh6GLKbspUEMV3xO0fNVG6FK/Zb vhm/urLL+AfVueMWsRsDMn0CJMoLFUajc8zy4T2a2GGbN0PszCjKgUOkEHzkNk7WqNni aLMiPRFg0n8qQOBfnAc3tqmeor7XrhyqffmR0aOHaFxT1RQ64P5fLJUWxD2f/pR6lfba XAsw4Hp1NR+m0DbWA3DnvCcWiCmODPNcZ4NgXXwydNkvdXiJX3kNkHOXiDzqMr6J/y1z 8OOw== ARC-Authentication-Results: i=1; mx.google.com; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=xmission.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 32-v6si9705561plh.70.2018.10.30.22.11.55; Tue, 30 Oct 2018 22:12:10 -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; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=xmission.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729162AbeJaN6G (ORCPT + 99 others); Wed, 31 Oct 2018 09:58:06 -0400 Received: from out01.mta.xmission.com ([166.70.13.231]:43247 "EHLO out01.mta.xmission.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728978AbeJaN6F (ORCPT ); Wed, 31 Oct 2018 09:58:05 -0400 Received: from in02.mta.xmission.com ([166.70.13.52]) by out01.mta.xmission.com with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.87) (envelope-from ) id 1gHidM-0000hB-Ne; Tue, 30 Oct 2018 23:01:36 -0600 Received: from 67-3-154-154.omah.qwest.net ([67.3.154.154] helo=x220.xmission.com) by in02.mta.xmission.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.87) (envelope-from ) id 1gHid7-0001Z2-Cf; Tue, 30 Oct 2018 23:01:36 -0600 From: ebiederm@xmission.com (Eric W. Biederman) To: Christian Brauner Cc: Daniel Colascione , Joel Fernandes , Linux Kernel Mailing List , Tim Murray , Suren Baghdasaryan References: <20181029221037.87724-1-dancol@google.com> <20181030103910.mnzot3zcoh6j7did@gmail.com> <20181030104037.73t5uz3piywxwmye@gmail.com> Date: Wed, 31 Oct 2018 00:00:51 -0500 In-Reply-To: (Christian Brauner's message of "Tue, 30 Oct 2018 12:19:51 +0100") Message-ID: <87h8h21zi4.fsf@xmission.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-XM-SPF: eid=1gHid7-0001Z2-Cf;;;mid=<87h8h21zi4.fsf@xmission.com>;;;hst=in02.mta.xmission.com;;;ip=67.3.154.154;;;frm=ebiederm@xmission.com;;;spf=neutral X-XM-AID: U2FsdGVkX18ocbg7AB8i1EGx2q5vpV3n5aF+D6ZRGTs= X-SA-Exim-Connect-IP: 67.3.154.154 X-SA-Exim-Mail-From: ebiederm@xmission.com X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on sa07.xmission.com X-Spam-Level: X-Spam-Status: No, score=-0.2 required=8.0 tests=ALL_TRUSTED,BAYES_50, DCC_CHECK_NEGATIVE,TVD_RCVD_IP,T_TM2_M_HEADER_IN_MSG autolearn=disabled version=3.4.1 X-Spam-Report: * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP * 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% * [score: 0.4050] * 0.0 TVD_RCVD_IP Message was received from an IP address * 0.0 T_TM2_M_HEADER_IN_MSG BODY: No description available. * -0.0 DCC_CHECK_NEGATIVE Not listed in DCC * [sa07 1397; Body=1 Fuz1=1 Fuz2=1] X-Spam-DCC: XMission; sa07 1397; Body=1 Fuz1=1 Fuz2=1 X-Spam-Combo: ;Christian Brauner X-Spam-Relay-Country: X-Spam-Timing: total 15034 ms - load_scoreonly_sql: 0.08 (0.0%), signal_user_changed: 3.5 (0.0%), b_tie_ro: 2.3 (0.0%), parse: 1.21 (0.0%), extract_message_metadata: 13 (0.1%), get_uri_detail_list: 1.71 (0.0%), tests_pri_-1000: 3.4 (0.0%), tests_pri_-950: 1.25 (0.0%), tests_pri_-900: 1.04 (0.0%), tests_pri_-90: 19 (0.1%), check_bayes: 18 (0.1%), b_tokenize: 6 (0.0%), b_tok_get_all: 6 (0.0%), b_comp_prob: 1.92 (0.0%), b_tok_touch_all: 2.7 (0.0%), b_finish: 0.64 (0.0%), tests_pri_0: 1137 (7.6%), check_dkim_signature: 0.55 (0.0%), check_dkim_adsp: 3.5 (0.0%), tests_pri_10: 3.1 (0.0%), tests_pri_500: 13848 (92.1%), poll_dns_idle: 13831 (92.0%), rewrite_mail: 0.00 (0.0%) Subject: Re: [RFC PATCH] Implement /proc/pid/kill X-Spam-Flag: No X-SA-Exim-Version: 4.2.1 (built Thu, 05 May 2016 13:38:54 -0600) X-SA-Exim-Scanned: Yes (on in02.mta.xmission.com) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Christian Brauner writes: > On Tue, Oct 30, 2018 at 12:12 PM Daniel Colascione wrote: >> >> On Tue, Oct 30, 2018 at 11:04 AM, Christian Brauner >> wrote: >> > On Tue, Oct 30, 2018 at 11:48 AM Daniel Colascione wrote: >> >> >> >> Why not? >> >> >> >> Does your proposed API allow for a race-free pkill, with arbitrary >> >> selection criteria? This capability is a good litmus test for fixing >> >> the long-standing Unix process API issues. >> > >> > You'd have a handle on the process with an fd so yes, it would be. >> >> Thanks. That's good to hear. >> >> Any idea on the timetable for this proposal? I'm open to lots of >> alternative technical approaches, but I don't want this capability to >> languish for a long time. > > Latest end of year likely sooner depending on the feedback I'm getting > during LPC. Frankly. If you want a race free fork variant probably the easiest thing to do is to return a open copy of the proc directory entry. Wrapped in a bind mount so that you can't see beyond that directory in proc. My only concern would be if a vfsmount per process would be too heavy for such a use. Eric