From: Marko Rauhamaa <marko.rauhamaa@f-secure.com>
To: <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] fanotify: introduce event flags FAN_EXEC and FAN_EXEC_PERM
Date: Mon, 16 Jul 2018 12:53:38 +0300 [thread overview]
Message-ID: <87fu0ja4m5.fsf@drapion.f-secure.com> (raw)
In-Reply-To: <1531731011.19075.11.camel@mbobrowski.org> (Matthew Bobrowski's message of "Mon, 16 Jul 2018 18:50:11 +1000")
Matthew Bobrowski <mbobrowski@mbobrowski.org>:
> 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
next prev parent reply other threads:[~2018-07-16 10:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 8:50 [PATCH] fanotify: introduce event flags FAN_EXEC and FAN_EXEC_PERM Matthew Bobrowski
2018-07-16 9:53 ` Marko Rauhamaa [this message]
2018-07-16 15:26 ` Jan Kara
2018-07-16 20:29 ` Steve Grubb
2018-07-17 12:44 ` Jan Kara
2018-07-17 13:36 ` Steve Grubb
2018-07-19 9:33 ` Jan Kara
2018-07-19 12:39 ` Steve Grubb
2018-07-19 13:06 ` Steve Grubb
2018-07-18 11:17 ` Matthew Bobrowski
2018-07-19 10:17 ` Jan Kara
2018-07-19 14:18 ` Marko Rauhamaa
2018-07-19 14:59 ` Steve Grubb
2018-07-17 12:21 ` Amir Goldstein
2018-07-17 12:48 ` Jan Kara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fu0ja4m5.fsf@drapion.f-secure.com \
--to=marko.rauhamaa@f-secure.com \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.