Hi Alex,
These two complementary APIs, FAN_REPORT_TARGET_FID (fanotify_init)
and FAN_RENAME (fanotify_mark) were merged to kernel v5.17.
Note that we used the fact that this is new API to fix a glitch that
exists in the old APIs - it is possble to request CREATE/DELETE/MOVE
events for a non-directrory, but those event can only be generated on
a directory.
When the new flags are used, ENOTDIR will be returned in such cases
and this change is reflected in the man pages updates.
However, we noticed this opportunity a bit late and the ENOTDIR change
was merged last minute to v5.18 and then backported to v5.17.9:
ceaf69f8eadc ("fanotify: do not allow setting dirent events in mask of
non-dir").
I did not mention this course of events in the man page, because it
seemed too much irrelevant information for end user, but am mentioning
it here for full disclosure in case somebody thinks this information is
relevant.
These patches apply on top of fan-fs-error branch in my tree [1]
which you have already reviewed, but have not yet applied.
[1] https://github.com/amir73il/man-pages/commits/fan-fs-error
Amir Goldstein (2):
fanotify.7, fanotify_init.2: Document FAN_REPORT_TARGET_FID
fanotify.7, fanotify_init.2, fanotify_mark.2: Document FAN_RENAME
man2/fanotify_init.2 | 53 +++++++++++++++++++++++++++++++++++++++++---
man2/fanotify_mark.2 | 23 +++++++++++++++++++
man7/fanotify.7 | 31 ++++++++++++++------------
3 files changed, 90 insertions(+), 17 deletions(-)
--
2.25.1
