From: Marko Rauhamaa <marko.rauhamaa@f-secure.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [RFC][PATCH 0/7] fanotify: add support for more events
Date: Mon, 17 Oct 2016 11:43:52 +0300 [thread overview]
Message-ID: <87oa2je56f.fsf@drapion.f-secure.com> (raw)
In-Reply-To: <CAOQ4uxhUk75Wh8o7o=kkYjq=-hTcs8y9GGHN9D=M93wcok8zYw@mail.gmail.com> (Amir Goldstein's message of "Sat, 15 Oct 2016 18:23:09 +0300")
Amir Goldstein <amir73il@gmail.com>:
> Let me rephrse my question - please argue why monitoring a file system
> instead of a mount point is important for your use case and more impotantly,
> please argue why you cannot achive the same result by monitoring all the
> relevant mount points from user space.
We are already doing that and missing fanotify events that are shrouded
by namespaces. Namespaces are popular through the use of containers, but
not only that. Distros are using namespaces to protect the private files
of services:
<URL: http://fedoraproject.org/wiki/Features/ServicesPrivateTmp>
<URL: https://access.redhat.com/blogs/766093/posts/1976243>.
> For example, the argument I used against the legacy recursive intotify
> watch of all directories in the treee is the poor ability to scale
> well over millions of directories.
Sure, that would be untenable. I'd argue the namespace issue is at least
equally tough because you'd have to keep monitoring namespaces deep
under the /proc hierarchy where processes come and go, there is no
epollable notification scheme available (to my knowledge) and race
conditions are inevitable. It would be virtually impossible for a
top-level fanotify monitor to keep track of what is going on.
Marko
next prev parent reply other threads:[~2016-10-17 8:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 17:35 [RFC][PATCH 0/7] fanotify: add support for more events Marko Rauhamaa
2016-10-13 18:42 ` Amir Goldstein
2016-10-14 8:28 ` Marko Rauhamaa
2016-10-15 15:23 ` Amir Goldstein
2016-10-17 8:43 ` Marko Rauhamaa [this message]
2016-12-09 9:14 ` Amir Goldstein
2016-12-09 13:16 ` Marko Rauhamaa
-- strict thread matches above, loose matches on Subject: below --
2016-10-10 19:12 Amir Goldstein
2016-10-11 7:00 ` Amir Goldstein
2016-10-11 11:32 ` Jan Kara
2016-10-12 11:49 ` Amir Goldstein
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=87oa2je56f.fsf@drapion.f-secure.com \
--to=marko.rauhamaa@f-secure.com \
--cc=amir73il@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox