From: Marko Rauhamaa <marko.rauhamaa@f-secure.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Jan Kara <jack@suse.cz>, Al Viro <viro@zeniv.linux.org.uk>,
Eric Paris <eparis@redhat.com>, <linux-fsdevel@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH 0/2] fsnotify: super block watch
Date: Wed, 21 Dec 2016 12:15:26 +0200 [thread overview]
Message-ID: <87bmw5ziyp.fsf@drapion.f-secure.com> (raw)
In-Reply-To: <1482247207-4424-1-git-send-email-amir73il@gmail.com> (Amir Goldstein's message of "Tue, 20 Dec 2016 17:20:05 +0200")
Amir Goldstein <amir73il@gmail.com>:
> On the Oct 10 posting you asked me about the use case and it was hard
> to explain the use case with only part of the work done.
>
> The issue, which this work sets to solve, is the poor scalability of
> recursive inotify watches.
On my [employer's] part, the fanotify API suffers from leakage through
namespaces.
If you need to monitor files in a filesystem, the current fanotify
FAN_MARK_MOUNT flag does not give you a notification if you execute a
command like
unshare -m touch xyz
inside the file system.
Amir's patch addresses this increasingly critical issue.
Marko
prev parent reply other threads:[~2016-12-21 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 15:20 [RFC][PATCH 0/2] fsnotify: super block watch Amir Goldstein
2016-12-20 15:20 ` [RFC][PATCH 1/2] fsnotify: add event mask FS_EVENT_ON_SB Amir Goldstein
2016-12-20 15:20 ` [RFC][PATCH 2/2] fsnotify: implement event reporting to super block's root inode Amir Goldstein
2016-12-21 10:15 ` Marko Rauhamaa [this message]
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=87bmw5ziyp.fsf@drapion.f-secure.com \
--to=marko.rauhamaa@f-secure.com \
--cc=amir73il@gmail.com \
--cc=eparis@redhat.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.