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.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=ham 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 572BDC28CC5 for ; Sat, 8 Jun 2019 10:55:12 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 18AC2212F5 for ; Sat, 8 Jun 2019 10:55:11 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=f-secure.com header.i=@f-secure.com header.b="SqZYcaPU" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726816AbfFHKzL (ORCPT ); Sat, 8 Jun 2019 06:55:11 -0400 Received: from helmsgagent01.f-secure.com ([193.110.108.21]:39266 "EHLO helmsgagent01.f-secure.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726692AbfFHKzL (ORCPT ); Sat, 8 Jun 2019 06:55:11 -0400 Received: from pps.filterd (helmsgagent01.f-secure.com [127.0.0.1]) by helmsgagent01.f-secure.com (8.16.0.27/8.16.0.27) with SMTP id x58AjRhh018286; Sat, 8 Jun 2019 13:55:08 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-secure.com; h=from : to : cc : subject : references : date : in-reply-to : message-id : mime-version : content-type; s=msg2048; bh=i/3ksBgyRsQfKYyp3CaQzD0ghbk5MpXhGs9qurwdDNI=; b=SqZYcaPU5NPxgFtOp21B2d/jzmx1c1FY39MpKv2b+fwTu/bh755//qncSBS5WPG1UUDl lp8YxfesEctffEsWivzCQjEFhNYSPMNotaPKAw64XyH3KTfiUVTnBnXkbxFR8v1Sy/qv B+V5zAR3YPDS20EsO1nx4Heyj0O/0t8OlrbspMBC6NpzyqBnbgC8ha15xaUzwtM/7sP0 y4p7IKMvdQn0qlhkgH7cz+7vpDc3rmTV1lU+3PRvi06An3ZZP48XjExf0k4jjcjDBnIu XAmEbuL0VIMnR2eBsOu/wUuQxPCNbDmotMhQwBNJ4Z8mSh1OvMkfbGkBPm35BuPv8AhJ fw== Received: from helex02.fi.f-secure.com ([10.190.48.73]) by helmsgagent01.f-secure.com with ESMTP id 2syykwrew0-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sat, 08 Jun 2019 13:55:08 +0300 Received: from drapion.f-secure.com (10.128.132.96) by helex01.FI.F-Secure.com (10.190.48.70) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sat, 8 Jun 2019 13:55:07 +0300 From: Marko Rauhamaa To: Amir Goldstein CC: linux-fsdevel Subject: Re: fanotify and pidfd? References: <87zhmt7bhc.fsf@drapion.f-secure.com> Date: Sat, 8 Jun 2019 13:55:07 +0300 In-Reply-To: (Amir Goldstein's message of "Fri, 7 Jun 2019 20:29:27 +0300") Message-ID: <87r28473ec.fsf@drapion.f-secure.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org Amir Goldstein : > On Fri, Jun 7, 2019 at 5:31 PM Marko Rauhamaa > wrote: >> Would it be possible to amend this format with: >> >> __s32 pidfd; >> > > It's possible to report pidfd instead of pid with user opt-in > (i.e. FAN_REPORT_PIDFD) > > If you want to implement this, follow the footsteps of code, test and > man page for FAN_REPORT_TID. I hear you. Marko