linux/fs/notify
Amir Goldstein 7232522e6c fanotify: store fsid in mark instead of in connector
Some filesystems like fuse and nfs have zero or non-unique fsid.
We would like to avoid reporting ambiguous fsid in events, so we need
to avoid marking objects with same fsid and different sb.

To make this easier to enforce, store the fsid in the marks of the group
instead of in the shared conenctor.

Signed-off-by: Amir Goldstein <amir73il@gmail.com>
Signed-off-by: Jan Kara <jack@suse.cz>
Message-Id: <20231130165619.3386452-2-amir73il@gmail.com>
2023-12-01 10:55:21 +01:00
..
dnotify As usual, lots of singleton and doubleton patches all over the tree and 2023-11-02 20:53:31 -10:00
fanotify fanotify: store fsid in mark instead of in connector 2023-12-01 10:55:21 +01:00
inotify treewide: mark stuff as __ro_after_init 2023-10-18 14:43:23 -07:00
fdinfo.c exportfs: add explicit flag to request non-decodeable file handles 2023-05-22 18:08:37 +02:00
fdinfo.h
fsnotify.c fsnotify: Fix comment typo 2022-07-26 13:38:47 +02:00
fsnotify.h fsnotify: remove unused declaration 2022-09-09 11:40:03 +02:00
group.c fsnotify: create helpers for group mark_mutex lock 2022-04-25 14:37:22 +02:00
Kconfig fs/notify: Remove "select SRCU" 2023-02-02 16:26:06 -08:00
Makefile
mark.c fanotify: store fsid in mark instead of in connector 2023-12-01 10:55:21 +01:00
notification.c fsnotify: Pass group argument to free_event 2021-10-27 12:34:18 +02:00