Skip to content

LTP fanotify tests for v6.13

Amir Goldstein ltp 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest5 patches 15 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/5fanotify13: Verify that we did not get an extra eventtestcases/kernel/syscalls/fanotify/fanotify13.c+19 -34 replies
2/5fanotify13: Add test case for FAN_DELETE_SELFtestcases/kernel/syscalls/fanotify/fanotify13.c+57 -110 replies
3/5fanotify05: Test reporting overflow event with FAN_REPORT_FD_ERRORinclude/lapi/fanotify.h testcases/kernel/syscalls/fanotify/fanotify.h testcases/kernel/syscalls/fanotify/fanotify05.c+21 -21 reply
4/5fanotify21: Test reporting event with RDWR fd on RO mounttestcases/kernel/syscalls/fanotify/fanotify21.c+32 -21 reply
5/5fanotify21: Test reporting fd open errors with FAN_REPORT_FD_ERRORtestcases/kernel/syscalls/fanotify/fanotify21.c+51 -101 reply

Reviews trailers per patch

3 of 5 patches have a Reviewed-by or Acked-by.

PatchPetr Vorel
1/5
2/5
3/5R-b
4/5R-b
5/5R-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [LTP] [PATCH 0/5] LTP fanotify tests for v6.13

Hi all,

Following tests for fanotify code in v6.13.

1. The new test case in fanotify13 fails as follows on kernels v6.6..v6.12:

fanotify13.c:282: TFAIL: handle_bytes (0) returned in event does not equal to handle_bytes (24) returned in name_to_handle_at(2) fanotify13.c:282: TFAIL: handle_bytes (0) returned in event does not equal to handle_bytes (24) returned in name_to_handle_at(2) fanotify13.c:282: TFAIL: handle_bytes (180003) returned in event does not equal to handle_bytes (24) returned in name_to_handle_at(2)

The fix was already backported to v6.12.10. It was also backported to v6.6.72,
but then reverted due to a backport bug in v6.6.73 and it now staged again for v6.6.74.

2. The new variant of fanotify21 is skipped on kernels <= v6.12

This variant tests the new feature flag FAN_REPORT_FD_ERROR, which is not effectively a bug fix.

Because this feature was added as a consequence of a bug report, it was auto backported to v6.12.5 and to v6.6.66, but I do not feel comfortable with adding a fix tag to force distros to backport this feature.

Thanks,
Amir.

Amir Goldstein (5):
fanotify13: Verify that we did not get an extra event
fanotify13: Add test case for FAN_DELETE_SELF
fanotify05: Test reporting overflow event with FAN_REPORT_FD_ERROR
fanotify21: Test reporting event with RDWR fd on RO mount
fanotify21: Test reporting fd open errors with FAN_REPORT_FD_ERROR

 include/lapi/fanotify.h                       |  4 +
 testcases/kernel/syscalls/fanotify/fanotify.h |  1 +
 .../kernel/syscalls/fanotify/fanotify05.c     | 18 +++-
 .../kernel/syscalls/fanotify/fanotify13.c     | 90 ++++++++++++++++---
 .../kernel/syscalls/fanotify/fanotify21.c     | 89 ++++++++++++++++--
 5 files changed, 177 insertions(+), 25 deletions(-)
Signature · 5 lines
2.34.1


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp