[LTP] fanotify01 test fails on nfsv3& nfsv4

Rhythm Mahajan rhythm.m.mahajan@oracle.com
Thu Feb 13 14:29:35 CET 2025


Hi,
fanotify01 test fails on nfsv3& nfsv4 for mainline 6.14 kernels.

mkdir /tmpdir
yum install nfs-utils  -y
echo "/media *(rw,no_root_squash,sync)" >/etc/exports
systemctl start nfs-server.service
mount -o rw,nfsvers=3 127.0.0.1:/media /tmpdir

cd /opt/ltp
./runltp -d /tmpdir  -s fanotify01

fanotify01.c:340: TFAIL: fanotify_mark(fd_notify, 0x00000001, 0x00000008, -100, ".") expected ENODEV: EXDEV (18)
fanotify01.c:340: TFAIL: fanotify_mark(fd_notify, 0x00000001, 0x00000008, -100, ".") expected ENODEV: EXDEV (18)
fanotify01.c:340: TFAIL: fanotify_mark(fd_notify, 0x00000001, 0x00000008, -100, ".") expected ENODEV: EXDEV (18)
fanotify01.c:340: TFAIL: fanotify_mark(fd_notify, 0x00000001, 0x00000008, -100, ".") expected ENODEV: EXDEV (18)
fanotify01.c:340: TFAIL: fanotify_mark(fd_notify, 0x00000001, 0x00000008, -100, ".") expected ENODEV: EXDEV (18)
fanotify01.c:340: TFAIL: fanotify_mark(fd_notify, 0x00000001, 0x00000008, -100, ".") expected ENODEV: EXDEV (18)
fanotify01.c:340: TFAIL: fanotify_mark(fd_notify, 0x00000001, 0x00000008, -100, ".") expected ENODEV: EXDEV (18)
fanotify01.c:340: TFAIL: fanotify_mark(fd_notify, 0x00000001, 0x00000008, -100, ".") expected ENODEV: EXDEV (18)
fanotify01.c:340: TFAIL: fanotify_mark(fd_notify, 0x00000001, 0x00000008, -100, ".") expected ENODEV: EXDEV (18)
fanotify01.c:340: TFAIL: fanotify_mark(fd_notify, 0x00000001, 0x00000008, -100, ".") expected ENODEV: EXDEV (18)
fanotify01.c:340: TFAIL: fanotify_mark(fd_notify, 0x00000001, 0x00000008, -100, ".") expected ENODEV: EXDEV (18)
fanotify01.c:340: TFAIL: fanotify_mark(fd_notify, 0x00000001, 0x00000008, -100, ".") expected ENODEV: EXDEV (18)
fanotify01.c:340: TFAIL: fanotify_mark(fd_notify, 0x00000001, 0x00000008, -100, ".") expected ENODEV: EXDEV (18)
fanotify01.c:340: TFAIL: fanotify_mark(fd_notify, 0x00000001, 0x00000008, -100, ".") expected ENODEV: EXDEV (18)
fanotify01.c:340: TFAIL: fanotify_mark(fd_notify, 0x00000001, 0x00000008, -100, ".") expected ENODEV: EXDEV (18)
fanotify01.c:340: TFAIL: fanotify_mark(fd_notify, 0x00000001, 0x00000008, -100, ".") expected ENODEV: EXDEV (18)
fanotify01.c:340: TFAIL: fanotify_mark(fd_notify, 0x00000001, 0x00000008, -100, ".") expected ENODEV: EXDEV (18)
fanotify01.c:340: TFAIL: fanotify_mark(fd_notify, 0x00000001, 0x00000008, -100, ".") expected ENODEV: EXDEV (18)
fanotify01.c:340: TFAIL: fanotify_mark(fd_notify, 0x00000001, 0x00000008, -100, ".") expected ENODEV: EXDEV (18)
fanotify01.c:340: TFAIL: fanotify_mark(fd_notify, 0x00000001, 0x00000008, -100, ".") expected ENODEV: EXDEV (18)
fanotify01.c:340: TFAIL: fanotify_mark(fd_notify, 0x00000001, 0x00000008, -100, ".") expected ENODEV: EXDEV (18)

We have been seeing this failure since 6.9

The test no longer fails with the revert of the commit
359047c97 fanotify01: Test setting two marks on different filesystems
https://github.com/linux-test-project/ltp/commit/359047c97

Could you please confirm if this is a test case issue or a kernel issue?

Thanks,
Rhythm


More information about the ltp mailing list