Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp2548560img; Sun, 24 Mar 2019 11:50:26 -0700 (PDT) X-Google-Smtp-Source: APXvYqxeagPFGXg/SJvEs1Gv6IzkygpGHjQU2mELIhg7rE86hNT9jTfdyj8qOMOZ9Cx258jZlGwe X-Received: by 2002:a17:902:e60e:: with SMTP id cm14mr21080569plb.192.1553453426590; Sun, 24 Mar 2019 11:50:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553453426; cv=none; d=google.com; s=arc-20160816; b=JPRWL+WfvP5eo86dTOEnzThVYFEH+DWfG3y1sSS8bTV0C97RxSuvTBB7OpQRqa2vwR LJPUEMIqo4imX9yDhY2PhfeGsMFyse6IXhHSZxcFtHVyVyc1/evdvnZxUBCoTY6rvg6r RvhkSFFVmVoJ25Ms0BG8t+IaFB1S+xnna47GoJrPZxOurLHJk4so0UHXkO4MMJkgU848 IjdGVEduAK43irbbr7yw9havqjNDEcnSLWCNdOZDu+glnRoAAZ2pUa8LWsKsevymjpg8 JP9sGusNx4OFAwXN447AIqdAxkk48rUgOFTnH3TDJhGWLNISE/U2hl4zK69GD08Zml7m wLNQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=3E5PbD/R8KE0AK8IEXA0HiRaTNZrWClh6JLvVEMcjJA=; b=LZ8WqqAAkNY7fpM28i1fHHpadBzzr4/E3iIqphzJFRz3DgDs/LTnHUOhodJHuoNITN Kv3LFn84gwMhhyZ3mlOWdBq+K04mklKUhDd4HVofR/nYgTHq+x47fFIDiUzNod66AM5O PT3fPNaThGQEJhn/vQeNL2VS1fEGYXi4z5mShYcNROn40N1ibZZrA69sM4xUpnm4LPGS /Kl6sFHN7Y0kTfVo1dLoBXNbGRICZ0UlNIuobwb+MYuQBlv4Q71oYPHD5mwk1FV7VF/B XplY0JnTsD+lxpmjJ5nn8d4eGi9c0U+bXgXdD26dibydVHRjvhIlR9q/XDUdF4xsYU0R ZPYg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=Kpr2Pj89; 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=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k72si3174711pgc.362.2019.03.24.11.50.12; Sun, 24 Mar 2019 11:50:26 -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=@google.com header.s=20161025 header.b=Kpr2Pj89; 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=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728956AbfCXStF (ORCPT + 99 others); Sun, 24 Mar 2019 14:49:05 -0400 Received: from mail-qt1-f170.google.com ([209.85.160.170]:44955 "EHLO mail-qt1-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726139AbfCXStE (ORCPT ); Sun, 24 Mar 2019 14:49:04 -0400 Received: by mail-qt1-f170.google.com with SMTP id w5so7905729qtb.11 for ; Sun, 24 Mar 2019 11:49:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3E5PbD/R8KE0AK8IEXA0HiRaTNZrWClh6JLvVEMcjJA=; b=Kpr2Pj89AACdsy9YXGxjPNM2856WloQP5gTnJGcMPHcDulRXB24JL1Q+55SZ8atsZ5 pTu+lL+XbvMqTKShWIDc2U1PeoFD/B0fTrhrmRmWHQL39Y2XUuH3WcWHArJ1fChakr8M +EQugGx8TeJA6+qHQWTme3C9lUj/6RhHLE8pKqo9CAO9rB/MTEFgfWe9ZuB4k7PmnI/k 7aJ3xsiegOQE/AqwkFIiHUTDJZZPTG8tjvyTShIZRB/ft+NCDYcNMITqGZilJqRKZHGJ kx++06XqoMPr0nh41EIxB69l6ghrb5N80kv2wK9f8K2619cn8tz2Rpgp8rzE15hkiie1 mkSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3E5PbD/R8KE0AK8IEXA0HiRaTNZrWClh6JLvVEMcjJA=; b=iwnMVVHw0SFALkvyMi3Jj7itRJYi95xFyTSv7t/xb/PTu04UE2zzumivkgMr/+AQP3 WZUIkabyVRa/LsFmL2P2tG0kS+5CvM4HWgKR0IEkJ3U7peyJZgl8Pbp6OYjn+YiC7o+k S5kJF/wVctSruYqjPsHPM42t5GwvGnM/dzA3A8vBnYxin0TiXQKcLnlRf4Em7jShXM3m rALuDYvpkddsdTiXw/NHcF6M9C7QBupqgg4PwpCrLHoTu446G1imojs7lLEJmyK++ZlV KnGl2zDchJEy0sBk/LNKGmg+ZPF8dRnZDB02FixKBx1ytF2Jz+XwUnJbd9UXluMQvD+W j5xw== X-Gm-Message-State: APjAAAVp61I1mAbzF9oFcoIH6GSAaAX/U9tWLmSQdWBYENvrJwB30NPz QETFB1rNiRFpNig/1t1motsRlJe7i9KQU7EifAudFw== X-Received: by 2002:a0c:d2fa:: with SMTP id x55mr17704481qvh.161.1553453343410; Sun, 24 Mar 2019 11:49:03 -0700 (PDT) MIME-Version: 1.0 References: <20190319231020.tdcttojlbmx57gke@brauner.io> <20190320015249.GC129907@google.com> <20190320035953.mnhax3vd47ya4zzm@brauner.io> <4A06C5BB-9171-4E70-BE31-9574B4083A9F@joelfernandes.org> <20190320182649.spryp5uaeiaxijum@brauner.io> <20190320185156.7bq775vvtsxqlzfn@brauner.io> <20190324144404.GA32603@mail.hallyn.com> In-Reply-To: <20190324144404.GA32603@mail.hallyn.com> From: Joel Fernandes Date: Sun, 24 Mar 2019 14:48:51 -0400 Message-ID: Subject: Re: pidfd design To: "Serge E. Hallyn" Cc: Daniel Colascione , Christian Brauner , Joel Fernandes , Suren Baghdasaryan , Steven Rostedt , Sultan Alsawaf , Tim Murray , Michal Hocko , Greg Kroah-Hartman , =?UTF-8?B?QXJ2ZSBIasO4bm5ldsOlZw==?= , Todd Kjos , Martijn Coenen , Ingo Molnar , Peter Zijlstra , LKML , "open list:ANDROID DRIVERS" , linux-mm , kernel-team , Oleg Nesterov , Andy Lutomirski , Kees Cook Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Mar 24, 2019 at 10:44 AM Serge E. Hallyn wrote: > > On Wed, Mar 20, 2019 at 12:29:31PM -0700, Daniel Colascione wrote: > > On Wed, Mar 20, 2019 at 11:52 AM Christian Brauner wrote: > > > I really want to see Joel's pidfd_wait() patchset and have more people > > > review the actual code. > > > > Sure. But it's also unpleasant to have people write code and then have > > to throw it away due to guessing incorrectly about unclear > > requirements. > > No, it is not. It is not unpleasant. And it is useful. It is the best way to > identify and resolve those incorrect guesses and unclear requirements. No problem, a bit of discussion helped set the direction. Personally it did help clarify lot of things for me. We are hard at work with come up with an implementation and are looking at posting something soon. I agree that the best is to discuss on actual code where possible.