fanotify09 case 3 (Events on files and dirs with both inode and mount marks) from ubuntu_ltp_syscalls failed
Bug #1876684 reported by
Po-Hsu Lin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-kernel-tests |
New
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
Xenial |
New
|
Undecided
|
Unassigned | ||
Bionic |
New
|
Undecided
|
Unassigned | ||
Eoan |
Fix Released
|
Undecided
|
Po-Hsu Lin | ||
Focal |
Fix Released
|
Undecided
|
Po-Hsu Lin |
Bug Description
This is a new test case added 7 days ago [1]
Test failed on Focal 5.4.0-29.33 with:
fanotify09.c:150: FAIL: group 1 got event: mask 10 pid=41059 fd=24 path=/tmp/
fanotify09.c:150: FAIL: group 2 got event: mask 10 pid=41059 fd=24 path=/tmp/
tags: | added: focal sru-20200427 ubuntu-ltp-syscalls |
summary: |
- fanotify09 case 3 failed on Focal + fanotify09 case 3 from ubuntu-ltp-syscalls failed on Focal |
summary: |
- fanotify09 case 3 from ubuntu-ltp-syscalls failed on Focal + fanotify09 case 3 from ubuntu_ltp_syscalls failed on Focal |
tags: | added: 5.4 |
summary: |
- fanotify09 case 3 from ubuntu_ltp_syscalls failed on Focal + fanotify09 case 3 from ubuntu_ltp_syscalls failed |
tags: | added: 5.3 eoan |
tags: | added: sru-20200921 |
tags: | added: 4.15 aws bionic |
tags: | added: sru-20210104 |
tags: | added: sru-20210621 |
summary: |
- fanotify09 case 3 from ubuntu_ltp_syscalls failed + fanotify09 case 3 (Events on files and dirs with both inode and mount + marks) from ubuntu_ltp_syscalls failed |
tags: | added: hinted |
tags: | added: sru-20211129 |
To post a comment you must log in.
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 1876684
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.