Re: [PATCH v2 0/2] Support fanotify FAN_REPORT_FID on all filesystems

[Jan Kara <jack@suse.cz>]

Hi!

On Thu 30-11-23 18:56:17, Amir Goldstein wrote:
> Jan,
> 
> In the vfs fanotify update for v6.7-rc1 [1], we considerably increased
> the amount of filesystems that can setup inode marks with FAN_REPORT_FID:
> - NFS export is no longer required for setting up inode marks
> - All the simple fs gained a non-zero fsid
> 
> This leaves the following in-tree filesystems where inode marks with
> FAN_REPORT_FID cannot be set:
> - nfs, fuse, afs, coda (zero fsid)
> - btrfs non-root subvol (fsid not a unique identifier of sb)
> 
> This patch set takes care of these remaining cases, by allowing inode
> marks, as long as all inode marks in the group are contained to the same
> filesystem and same fsid (i.e. subvol).
> 
> I've written some basic sanity tests [2] and a man-page update draft [3].
> The LTP tests excersize the new code by running tests that did not run
> before on ntfs-3g fuse filesystem and skipping the test cases with mount
> and sb marks.
> 
> I've also tested fsnotifywait --recursive on fuse and on btrfs subvol.
> It works as expected - if tree travesal crosses filesystem or subvol
> boundary, setting the subdir mark fails with -EXDEV.

Now all the patches have arrived. Queued into my tree.

								Honza
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR