All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 19 Jul 2018 17:18:26 +0300	[thread overview]
Message-ID: <871sbz9uml.fsf@drapion.f-secure.com> (raw)
In-Reply-To: <20180719101708.ad754qhekwoyanps@quack2.suse.cz> (Jan Kara's message of "Thu, 19 Jul 2018 12:17:08 +0200")

Jan Kara <jack@suse.cz>:
> So fanotify is a filesystem event notification API. For filesystem,
> open and read are fundamentally different events and as such we have
> different FAN_OPEN and FAN_ACCESS events in the API. The only
> disputable events we have in the API are FAN_CLOSE_WRITE vs
> FAN_CLOSE_NOWRITE - from fs POV there's no big difference. But at
> least this is 100% reliably (unlike FMODE_EXEC) telling you whether
> the user was able to modify the file or not and it caters to one of
> the use cases this API has been created for - virus scanners, file
> caching daemons, ... - i.e., triggering specific actions based on file
> contents.

As a side note from the virus scanner point of view,
FAN_CLOSE_WRITE_PERM would be really useful because it would prevent the
hit-and-run corruption of a file. As it stands, fanotify communicates
the pid of the culprit but the process is long gone by the time you get
to analyze it...


Marko

  reply	other threads:[~2018-07-19 15:01 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
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 [this message]
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=871sbz9uml.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.