From: Marko Rauhamaa <marko.rauhamaa@f-secure.com>
To: <linux-fsdevel@vger.kernel.org>
Cc: <amir73il@gmail.com>
Subject: Re: [RFC][PATCH 0/7] fanotify: add support for more events
Date: Thu, 13 Oct 2016 20:35:43 +0300 [thread overview]
Message-ID: <87inswm9sg.fsf@drapion.f-secure.com> (raw)
Amir Goldstein:
> This series is a prep work for using fanotify to monitor all events in
> a file system with a single watch.
>
> [...]
>
> I am posting this WIP to get feedback on the idea and to find out if
> there are any users out there interested in the improved fanotify
> capabilities and/or in the super block monitoring use case.
My employer certainly is in need of monitoring a whole filesystem. We
have noticed that namespaces evade monitoring via FAN_MARK_MOUNT. I was
thinking something like a FAN_MARK_FILESYSTEM would be needed.
(There are some other needed features but filesystem monitoring is the
most pressing one.)
Jan Kara:
> Careful here. In the world of user namespaces and containers you have
> to be really careful so that events from one container don't leak into
> another container despite they live in the same physical filesystem,
> just a different bind mount.
Obviously, proper care needs to be taken, but a namespace should not be
able smuggle filesystem events past fanotify monitoring.
Marko
next reply other threads:[~2016-10-13 18:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 17:35 Marko Rauhamaa [this message]
2016-10-13 18:42 ` [RFC][PATCH 0/7] fanotify: add support for more events Amir Goldstein
2016-10-14 8:28 ` Marko Rauhamaa
2016-10-15 15:23 ` Amir Goldstein
2016-10-17 8:43 ` Marko Rauhamaa
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=87inswm9sg.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