> Please post the series now since there were quite some changes (although > smaller ones) since the last posting. I'll go through it and push it to my > tree. Do we already have LTP tests for the new functionality? I'd like to > do some testing before pushing things out... Yes there are LTP tests you can use. I'll use this opportunity to dump the content of my LTP dev branch and recap the WIP (mainly by Matthew) on fanotify LTP tests: * 9eb01c6b4 - (HEAD -> fanotify_dirent, github/fanotify_dirent) syscalls/fanotify102: new test for dirent events * 2218e949c - (github/fanotify_fid, fanotify_fid) syscalls/fanotify14: new test to validate FAN_REPORT_FID interface return values * b7ad5c4fe - syscalls/fanotify13: new test to verify FAN_REPORT_FID functionality * 10abf45c1 - syscalls/fanotify01: add FAN_REPORT_FID test cases * 9185a0aa1 - (github/fanotify_exec, fanotify_exec) syscalls/fanotify10: increase test coverage to support FAN_OPEN_EXEC mask * cd7ab20d5 - syscalls/fanotify12: add new test to support new FAN_OPEN_EXEC event mask * 56ba122c0 - syscalls/fanotify03: add FAN_OPEN_EXEC_PERM tcase support * f596b4a5d - syscalls/fanotify03: included execve() to generate_events() to increase test coverage * f23d990ad - syscalls/fanotify03: defined additional tcase members to support more tcase control * 7846bbbed - syscalls/fanotify03: add test for FAN_MARK_FILESYSTEM permission events fanotify_exec branch has Matthew's tests for FAN_OPEN_EXEC. Following request from LTP maintainer, he will post them around v5.0-rc3 time. fanotify_fid branch has 2 new FAN_REPORT_FID tests by Matthew, which verify the functionality of reporting fid. fanotify_dirent branch has 1 WIP test to verify new events functionality. its temporary name fanotify102 goes after the test inotify02 which verifies similar functionality with inotify. Matthew is going to work this test into shape and add verification that the reported fid in dirent events (and _SELF events) is correct. Thanks, Amir.
