linux-kernel - Re: fanotify and namespaces/bind mounts

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]

Date:   Sat, 18 Mar 2017 10:04:00 -0400
From:   riya khanna <riyakhanna1983@...il.com>
To:     Marko Rauhamaa <marko@...ujo.net>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: fanotify and namespaces/bind mounts

Are fsnotify events generated per mount namespace?

On Thu, Oct 29, 2015 at 9:29 AM, Marko Rauhamaa <marko@...ujo.net> wrote:
>
> If I call fanotify_mark(... FAN_MARK_ADD | FAN_MARK_MOUNT ...), I get
> notifications on all files on the file system.
>
> Except I don't.
>
> If a process has mounted directories on the file system in a different
> namespace, the global namespace experiences file system events but no
> fanotify events are generated. A similar limitation applies to bind
> mounts.
>
> You can easily see this behavior in action. Do "man fanotify", and copy
> the example program to, say, example.c. Then,
>
>     cc -o example example.c
>     mkdir -p /mnt/xyz
>     mount -o bind /root /mnt/xyz
>     ./example /root
>
> The last command prints out fanotify events. It will display events for
>
>     touch /root/xyzzy
>
> but nothing for
>
>     touch /mnt/xyz/zyxxy
>
> or
>
>     unshare -m touch /root/yxyyx
>
> Should the current situation be considered a bug in fanotify? Or is
> there another recommended way to monitor file system events
> categorigally?
>
>
> Marko
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/