All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: [RFC] Volatile fanotify marks
Date: Wed, 23 Feb 2022 20:42:37 +0200	[thread overview]
Message-ID: <CAOQ4uxiRDpuS=2uA6+ZUM7yG9vVU-u212tkunBmSnP_u=mkv=Q@mail.gmail.com> (raw)

Hi Jan,

I wanted to get your feedback on an idea I have been playing with.
It started as a poor man's alternative to the old subtree watch problem.
For my employer's use case, we are watching the entire filesystem using
a filesystem mark, but would like to exclude events on a subtree
(i.e. all files underneath .private/).

At the moment, those events are filtered in userspace.
I had considered adding directory marks with an ignored mask on every
event that is received for a directory path under .private/, but that has the
undesired side effect of pinning those directory inodes to cache.

I have this old fsnotify-volatile branch [1] that I am using for an overlayfs
kernel internal fsnotify backend. I wonder what are your thoughts on
exposing this functionally to fanotify UAPI (i.e. FAN_MARK_VOLATILE).

Thanks,
Amir.

[1] https://github.com/amir73il/linux/commits/fsnotify-volatile

             reply	other threads:[~2022-02-23 18:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23 18:42 Amir Goldstein [this message]
2022-02-28 14:05 ` [RFC] Volatile fanotify marks Jan Kara
2022-02-28 17:40   ` Amir Goldstein
2022-03-01 11:07     ` Jan Kara
2022-03-01 11:27       ` Amir Goldstein
2022-03-01 12:26     ` Tycho Kirchner
2022-03-01 16:58       ` Amir Goldstein
2022-03-02 10:04         ` Tycho Kirchner
2022-03-02 18:14           ` Amir Goldstein
2022-03-03  9:24             ` Jan Kara
2022-05-02  9:13               ` Tycho Kirchner
2022-05-04  6:13                 ` Amir Goldstein
2022-05-04 10:01                   ` Tycho Kirchner
2022-05-04 14:37                     ` Amir Goldstein
2022-05-06  9:59                       ` Tycho Kirchner
2022-05-05 10:42                     ` Jan Kara
2022-05-13 15:30   ` Matthew Bobrowski

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='CAOQ4uxiRDpuS=2uA6+ZUM7yG9vVU-u212tkunBmSnP_u=mkv=Q@mail.gmail.com' \
    --to=amir73il@gmail.com \
    --cc=jack@suse.cz \
    --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.