Skip to contentSkip to conversation

fanotify and namespaces/bind mounts

DISCUSSION Marko Rauhamaa 2 participants 2 messages Oct 29, 2015 – Mar 18, 2017

lore
Share & tools
lore
#0 lore raw

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

#1 lore raw

Are fsnotify events generated per mount namespace?

Quoted 42 lines · Marko Rauhamaa

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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/