fanotify11 in ubuntu_ltp_syscalls failed

[Po-Hsu Lin]

Timeouted on Trusty:
 startup='Tue Dec 11 11:58:36 2018'
 tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
 fanotify11.c:85: INFO: without FAN_REPORT_TID: tgid=5447, tid=5448, event.pid=5447
 fanotify11.c:89: PASS: event.pid == tgid
 Test timeouted, sending SIGKILL!
 Test timeouted, sending SIGKILL!
 Test timeouted, sending SIGKILL!
 Test timeouted, sending SIGKILL!
 Test timeouted, sending SIGKILL!
 Test timeouted, sending SIGKILL!
 Test timeouted, sending SIGKILL!
 Test timeouted, sending SIGKILL!
 Test timeouted, sending SIGKILL!
 Test timeouted, sending SIGKILL!
 Test timeouted, sending SIGKILL!
 Cannot kill test processes!
 Congratulation, likely test hit a kernel bug.
 Exitting uncleanly...
 tag=fanotify11 stime=1544529516 dur=350 exit=exited stat=1 core=no cu=0 cs=0

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1808107

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Po-Hsu Lin (cypressyew)]

The test will pass if you run this directly:
tag=fanotify11 stime=1562574226
cmdline="fanotify11"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
fanotify11.c:66: INFO: Test #0: without FAN_REPORT_TID: tgid=2380, tid=0, event.pid=0
fanotify11.c:91: PASS: event.pid == tgid
fanotify11.c:66: INFO: Test #1: with FAN_REPORT_TID: tgid=2380, tid=2381, event.pid=2380
fanotify11.c:72: CONF: FAN_REPORT_TID not supported in kernel?

Summary:
passed 1
failed 0
skipped 1
warnings 0
<<<execution_status>>>
initiation_status="ok"

So this timeout failure is probably caused by some failures (fanotify07 or fanotify08) before this test.

[Po-Hsu Lin (cypressyew)]

Mark this as invalid for Xenial, this issue should be tracked in bug 1775165 for fanotify07