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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <87bmw5ziyp.fsf@drapion.f-secure.com>
Date:   Wed, 21 Dec 2016 12:15:26 +0200
From:   Marko Rauhamaa <marko.rauhamaa@...ecure.com>
To:     Amir Goldstein <amir73il@...il.com>
CC:     Jan Kara <jack@...e.cz>, Al Viro <viro@...iv.linux.org.uk>,
        Eric Paris <eparis@...hat.com>,
        <linux-fsdevel@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [RFC][PATCH 0/2] fsnotify: super block watch

Amir Goldstein <amir73il@...il.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