An F-Secure product uses fanotify with OPEN_PERM. We ran into an unexpected situation: a read(2) on the fanotify fd returned -1 with errno == EOPENSTALE. The only place in the (development) kernel where I can find EOPENSTALE is in nfs4file.c:nfs4_file_open(). Questions: * Should an fanotify client expect EOPENSTALE from read(2)? * According to <URL: https://github.com/torvalds/linux/blob/master/include/linux/errno.h>, EOPENSTALE "should never be seen by user programs." Is this a kernel bug? * The kernel in question is kernel-3.10.0-229.el7.x86_64 (RHEL 7.3). I will take it up with Red Hat if necessary. However, is this a known issue that has been fixed in a newer kernel version? Marko
