Re: [RFC][PATCH 0/2] fsnotify: super block watch

From	Marko Rauhamaa <marko.rauhamaa@f-secure.com>
Newsgroups	linux.kernel
Subject	Re: [RFC][PATCH 0/2] fsnotify: super block watch
Date	2016-12-21 11:40 +0100
Message-ID	<sQMts-2bQ-17@gated-at.bofh.it> (permalink)
References	<sQuwx-7jd-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

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

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

[RFC][PATCH 0/2] fsnotify: super block watch Amir Goldstein <amir73il@gmail.com> - 2016-12-20 16:30 +0100
  [RFC][PATCH 2/2] fsnotify: implement event reporting to super block's root inode Amir Goldstein <amir73il@gmail.com> - 2016-12-20 16:30 +0100
  [RFC][PATCH 1/2] fsnotify: add event mask FS_EVENT_ON_SB Amir Goldstein <amir73il@gmail.com> - 2016-12-20 16:30 +0100
  Re: [RFC][PATCH 0/2] fsnotify: super block watch Marko Rauhamaa <marko.rauhamaa@f-secure.com> - 2016-12-21 11:40 +0100

csiph-web