From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C58C2C10F11 for ; Wed, 24 Apr 2019 08:06:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9E87B218D3 for ; Wed, 24 Apr 2019 08:06:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727329AbfDXIGU (ORCPT ); Wed, 24 Apr 2019 04:06:20 -0400 Received: from mout.kundenserver.de ([212.227.126.135]:52161 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726904AbfDXIGT (ORCPT ); Wed, 24 Apr 2019 04:06:19 -0400 Received: from [192.168.1.115] ([95.114.95.254]) by mrelayeu.kundenserver.de (mreue009 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MV6G6-1hCARK2U46-00S4C7; Wed, 24 Apr 2019 10:04:32 +0200 Subject: Re: [PATCH RFC 1/2] Add polling support to pidfd To: Daniel Colascione , Joel Fernandes Cc: Christian Brauner , Jann Horn , Oleg Nesterov , Florian Weimer , kernel list , Andy Lutomirski , Steven Rostedt , Suren Baghdasaryan , Linus Torvalds , Alexey Dobriyan , Al Viro , Andrei Vagin , Andrew Morton , Arnd Bergmann , "Eric W. Biederman" , Kees Cook , linux-fsdevel , "open list:KERNEL SELFTEST FRAMEWORK" , Michal Hocko , Nadav Amit , Serge Hallyn , Shuah Khan , Stephen Rothwell , Taehee Yoo , Tejun Heo , Thomas Gleixner , kernel-team , Tycho Andersen References: <20190416120430.GA15437@redhat.com> <20190416192051.GA184889@google.com> <20190417130940.GC32622@redhat.com> <20190419190247.GB251571@google.com> <20190419191858.iwcvqm6fihbkaata@brauner.io> <20190419194902.GE251571@google.com> <20190419212002.GB44851@google.com> From: "Enrico Weigelt, metux IT consult" Organization: metux IT consult Message-ID: <34c493c3-993f-39f1-3afc-7f59d5113a30@metux.net> Date: Wed, 24 Apr 2019 10:04:27 +0200 User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:jHk41HQrf7eFSMcKEW+gYQHxdGt0dojWSCn9QycWmgOukdN9B/+ UXIlQ2ddjTGxLLKg6cMjiuWG1wW+6RAVoice/8n0FOMODPfKIApg9lZDFbeY8hzlRwERYHC icwzfoPmd4W4o+asNiLBZzRknwKIagmAMuYnVu4iznkgl/d5yqcW82DXdTMfRv6UCbESYf1 8jGlZGWAbQB5yQI8Yd2hw== X-UI-Out-Filterresults: notjunk:1;V03:K0:9TI3qhE1U9A=:Hn4c2h+O6WIDupvtLoKx45 +DT77Bz0ob2JWX32qoNDM6oTwe13ksWarqnCWD7cvlipGwGUafYFXkF17hvMaQVR/XkKDTQhE TXL/X7BnUfgaasS76rBoooqJPnc8qnZClWb6P6uLoDddz10EKTaCIVIoYYtR1/7RUnpVw1geG MIgDMb02I1LGm8ok1e+aOIV0If4rPX/p10KZmzIY0Zf8unNJ9a/XIsPvqfunmscNLBp68vkO1 1iU1/b73jxqAwzJ+fueft8/eBQgMV+9X0f5dyiziHoYW/qj8AcfhoyToOSGR79e2LMFjYxD3J qEi6TVbojffiWaa2Tx11cpgbamXTLpnkjJSbrR3xsV4Vvjqi1feWclLHCdEDqQTfltEZHOtUE o70kwhTzCME9h+qDrT71fuVLYrPX+1FOWG1M04Hf6i9aaR+Y9aVtAs4OkT467IFdn6vFWbUpk zVOgbwqCPNzWK4kmmapcGVa1pF5Q2K34BqYiBiC1QO4DSQ7MeraPoEm4VpIezyjXrLtFC/xZG YxqxQ6NvNnWkAxIJ7duHb4JvyBEyt/JfzAtGxorWO7fJVGukt38iaXr5B5PeIGT9bBEVkXZlH gFb0Lak3xo+hRl9B8cN+FlZtuZkZW59AoR8KLS0cwusHQV24GYU8ZKOTnZBXJ/2bp5+tdXGN6 ZuyxdeeaqpW29pfGGlTyOzq5dEeOwplxEE3/FX4fqu/AACIIn3jHWqRuCcDfRRx8F1g7QgvVD mWRaKck/Kb4OGQHvj5vOCY4txsbM7SyKEcQthJNTXGa7AnIi5yhJkKsxxt4= Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On 19.04.19 23:24, Daniel Colascione wrote: Hi folks, I haven't followed the whole thread, so forgive me if I'm going to write something dumb here ... but: this all feels a bit complicated to me. Why not just making the pidfd present a stream of events (which are encoded as text lines) ? It would behave just like any stream, eg. socket, chardev, ... An `cat` on a pidfd could look like this: EXIT EXEC SIGNAL ... IOW: just using POLLIN. Let the listener just read all events and decide which ones he's actually acting on. In the other direction we could write in commands, eg. for sending signals. --mtx -- Enrico Weigelt, metux IT consult Free software and Linux embedded engineering info@metux.net -- +49-151-27565287