From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from helmsgmaster01.f-secure.com ([193.110.108.20]:40138 "EHLO helmsgmaster01.f-secure.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726851AbeGPKZ7 (ORCPT ); Mon, 16 Jul 2018 06:25:59 -0400 Received: from pps.filterd (helmsgmaster01.f-secure.com [127.0.0.1]) by helmsgmaster01.f-secure.com (8.16.0.21/8.16.0.21) with SMTP id w6G9pT34022221 for ; Mon, 16 Jul 2018 12:53:44 +0300 Received: from helex02.fi.f-secure.com ([10.190.48.73]) by helmsgmaster01.f-secure.com with ESMTP id 2k8aukrr5j-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for ; Mon, 16 Jul 2018 12:53:44 +0300 From: Marko Rauhamaa To: Subject: Re: [PATCH] fanotify: introduce event flags FAN_EXEC and FAN_EXEC_PERM References: <1531731011.19075.11.camel@mbobrowski.org> Date: Mon, 16 Jul 2018 12:53:38 +0300 In-Reply-To: <1531731011.19075.11.camel@mbobrowski.org> (Matthew Bobrowski's message of "Mon, 16 Jul 2018 18:50:11 +1000") Message-ID: <87fu0ja4m5.fsf@drapion.f-secure.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Matthew Bobrowski : > Currently, the fanotify API does not provide a means for user space > programs to register and receive events specifically when a file has > been opened with the intent to be executed. Two new event flags > FAN_EXEC and FAN_EXEC_PERM have been introduced to the fanotify API > along with updates to the generic filesystem notification hooks > fsnotify_open and fsnotify_perm in order to support this capability. Does this affect: * executable shebang files (files starting with #!) * interpreted files: - bash ./xyzzy.sh - java xyzzy.jar - python3 xyzzy.py Marko