[Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
Still visible in Xenial 4.4.0-1118.132 AWS c5.metal ** Tags added: sru-20201109 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802454 Title: fanotify10 in ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
** Tags added: sru-20200629 sru-20200720 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802454 Title: fanotify10 in ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
For the failure of test case #16 on Focal, please check bug 1882717 ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802454 Title: fanotify10 in ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
** Tags added: sru-20200316 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802454 Title: fanotify10 in ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
Test result on Trusty: startup='Sat Oct 5 00:28:40 2019' tst_device.c:238: INFO: Using test device LTP_DEV='/dev/loop0' tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts='' mke2fs 1.42.9 (4-Feb-2014) tst_test.c:1118: INFO: Timeout per run is 0h 05m 00s fanotify10.c:331: INFO: Test #0: ignore mount events created on a specific file fanotify10.c:292: PASS: group 0 got event: mask 20 pid=8205 fd=30 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=8205 fd=30 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=8205 fd=30 fanotify10.c:398: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:398: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:398: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:398: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:398: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:398: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:331: INFO: Test #1: ignore exec mount events created on a specific file fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel? fanotify10.c:331: INFO: Test #2: don't ignore mount events created on another file fanotify10.c:292: PASS: group 0 got event: mask 20 pid=8206 fd=30 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=8206 fd=30 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=8206 fd=30 fanotify10.c:292: PASS: group 0 got event: mask 20 pid=8206 fd=30 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=8206 fd=30 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=8206 fd=30 fanotify10.c:292: PASS: group 0 got event: mask 20 pid=8206 fd=30 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=8206 fd=30 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=8206 fd=30 fanotify10.c:331: INFO: Test #3: don't ignore exec mount events created on another file fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel? fanotify10.c:331: INFO: Test #4: ignore inode events created on a specific mount point fanotify10.c:292: PASS: group 0 got event: mask 20 pid=8207 fd=30 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=8207 fd=30 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=8207 fd=30 fanotify10.c:392: FAIL: group 0 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event fanotify10.c:392: FAIL: group 1 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event fanotify10.c:392: FAIL: group 2 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event fanotify10.c:392: FAIL: group 0 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event fanotify10.c:392: FAIL: group 1 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event fanotify10.c:392: FAIL: group 2 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event fanotify10.c:331: INFO: Test #5: ignore exec inode events created on a specific mount point fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel? fanotify10.c:331: INFO: Test #6: don't ignore inode events created on another mount point fanotify10.c:292: PASS: group 0 got event: mask 20 pid=8208 fd=30 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=8208 fd=30 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=8208 fd=30 fanotify10.c:292: PASS: group 0 got event: mask 20 pid=8208 fd=30 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=8208 fd=30 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=8208 fd=30 fanotify10.c:292: PASS: group 0 got event: mask 20 pid=8208 fd=30 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=8208 fd=30 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=8208 fd=30 fanotify10.c:331: INFO: Test #7: don't ignore exec inode events created on another mount point fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel? fanotify10.c:331: INFO: Test #8: ignore fs events created on a specific file fanotify10.c:232: CONF: FAN_MARK_FILESYSTEM not supported in kernel? fanotify10.c:331: INFO: Test #9: ignore exec fs events created on a specific file fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel? fanotify10.c:331: INFO: Test #10: don't ignore mount events created on another file fanotify10.c:232: CONF: FAN_MARK_FILESYSTEM not supported in kernel? fanotify10.c:331: INFO: Test #11: don't ignore exec mount events created on another file fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel? fanotify10.c:331: INFO: Test #12: ignore fs events created on a specific mount point fanotify10.c:232: CONF: FAN_MARK_FILESYSTEM not supported in kernel? fanotify10.c:331: INFO: Test #13: ignore exec fs events created on a specific mount point
[Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
** Changed in: ubuntu-kernel-tests Status: In Progress => Confirmed ** Changed in: ubuntu-kernel-tests Assignee: Po-Hsu Lin (cypressyew) => (unassigned) ** Tags added: ubuntu-ltp-syscalls -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802454 Title: fanotify10 in ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
** Tags added: cscc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802454 Title: fanotify10 in ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
For Xenial 4.4, if you run this test after a clean reboot you will get: <>> tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop0' incrementing stop tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts='' mke2fs 1.42.13 (17-May-2015) tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s fanotify10.c:331: INFO: Test #0: ignore mount events created on a specific file fanotify10.c:292: PASS: group 0 got event: mask 20 pid=3049 fd=15 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=3049 fd=15 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=3049 fd=15 fanotify10.c:398: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:398: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:398: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:398: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:398: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:398: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:331: INFO: Test #1: ignore exec mount events created on a specific file fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel? fanotify10.c:331: INFO: Test #2: don't ignore mount events created on another file fanotify10.c:292: PASS: group 0 got event: mask 20 pid=3050 fd=15 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=3050 fd=15 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=3050 fd=15 fanotify10.c:292: PASS: group 0 got event: mask 20 pid=3050 fd=15 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=3050 fd=15 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=3050 fd=15 fanotify10.c:292: PASS: group 0 got event: mask 20 pid=3050 fd=15 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=3050 fd=15 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=3050 fd=15 fanotify10.c:331: INFO: Test #3: don't ignore exec mount events created on another file fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel? fanotify10.c:331: INFO: Test #4: ignore inode events created on a specific mount point fanotify10.c:292: PASS: group 0 got event: mask 20 pid=3051 fd=15 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=3051 fd=15 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=3051 fd=15 fanotify10.c:392: FAIL: group 0 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event fanotify10.c:392: FAIL: group 1 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event fanotify10.c:392: FAIL: group 2 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event fanotify10.c:392: FAIL: group 0 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event fanotify10.c:392: FAIL: group 1 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event fanotify10.c:392: FAIL: group 2 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got event fanotify10.c:331: INFO: Test #5: ignore exec inode events created on a specific mount point fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel? fanotify10.c:331: INFO: Test #6: don't ignore inode events created on another mount point fanotify10.c:292: PASS: group 0 got event: mask 20 pid=3052 fd=15 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=3052 fd=15 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=3052 fd=15 fanotify10.c:292: PASS: group 0 got event: mask 20 pid=3052 fd=15 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=3052 fd=15 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=3052 fd=15 fanotify10.c:292: PASS: group 0 got event: mask 20 pid=3052 fd=15 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=3052 fd=15 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=3052 fd=15 fanotify10.c:331: INFO: Test #7: don't ignore exec inode events created on another mount point fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel? fanotify10.c:331: INFO: Test #8: ignore fs events created on a specific file fanotify10.c:232: CONF: FAN_MARK_FILESYSTEM not supported in kernel? fanotify10.c:331: INFO: Test #9: ignore exec fs events created on a specific file fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel? fanotify10.c:331: INFO: Test #10: don't ignore mount events created on another file fanotify10.c:232: CONF: FAN_MARK_FILESYSTEM not supported in kernel? fanotify10.c:331: INFO: Test #11: don't ignore exec mount events created on another file fanotify10.c:226: CONF: FAN_OPEN_EXEC not supported by kernel? fanotify10.c:331: INFO: Test #12: ignore fs events created on a specific mount point fanotify10.c:232: CONF: FAN_MARK_FILESYSTEM not supported in kernel? fanotify10.c:331: INFO: Test #13: ignore exec fs events created on a specific mount point fanotify10.c:226: CONF: FAN_OPEN_EXEC not
[Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
For Trusty-4.4 test timeouted. startup='Fri Mar 22 02:07:25 2019' tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop0' tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts='' mke2fs 1.42.9 (4-Feb-2014) tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s fanotify10.c:331: INFO: Test #0: ignore mount events created on a specific file fanotify10.c:292: PASS: group 0 got event: mask 20 pid=10758 fd=30 fanotify10.c:292: PASS: group 1 got event: mask 20 pid=10758 fd=30 fanotify10.c:292: PASS: group 2 got event: mask 20 pid=10758 fd=30 fanotify10.c:398: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:398: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:398: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:398: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:398: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:398: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event 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... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802454 Title: fanotify10 in ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
For cosmic it's been fixed in stable updates: 9aa2a0a66f6f5f5b5d12e9cbd7caff7385cd6179 fsnotify: fix ignore mask logic in fsnotify() ** Changed in: linux (Ubuntu Cosmic) Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802454 Title: fanotify10 in ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
This bug was fixed in the package linux - 4.15.0-44.47
---
linux (4.15.0-44.47) bionic; urgency=medium
* linux: 4.15.0-44.47 -proposed tracker (LP: #1811419)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
- blk-wbt: pass in enum wbt_flags to get_rq_wait()
- blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait
- blk-wbt: move disable check into get_limit()
- blk-wbt: use wq_has_sleeper() for wq active check
- blk-wbt: fix has-sleeper queueing check
- blk-wbt: abstract out end IO completion handler
- blk-wbt: improve waking of tasks
* To reduce the Realtek USB cardreader power consumption (LP: #1811337)
- mmc: sdhci: Disable 1.8v modes (HS200/HS400/UHS) if controller can't
support
1.8v
- mmc: core: Introduce MMC_CAP_SYNC_RUNTIME_PM
- mmc: rtsx_usb_sdmmc: Don't runtime resume the device while changing led
- mmc: rtsx_usb: Use MMC_CAP2_NO_SDIO
- mmc: rtsx_usb: Enable MMC_CAP_ERASE to allow erase/discard/trim requests
- mmc: rtsx_usb_sdmmc: Re-work runtime PM support
- mmc: rtsx_usb_sdmmc: Re-work card detection/removal support
- memstick: rtsx_usb_ms: Add missing pm_runtime_disable() in probe function
- misc: rtsx_usb: Use USB remote wakeup signaling for card insertion
detection
- memstick: Prevent memstick host from getting runtime suspended during card
detection
- memstick: rtsx_usb_ms: Use ms_dev() helper
- memstick: rtsx_usb_ms: Support runtime power management
* Support non-strict iommu mode on arm64 (LP: #1806488)
- iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
- iommu/arm-smmu-v3: Implement flush_iotlb_all hook
- iommu/dma: Add support for non-strict mode
- iommu: Add "iommu.strict" command line option
- iommu/io-pgtable-arm: Add support for non-strict mode
- iommu/arm-smmu-v3: Add support for non-strict mode
- iommu/io-pgtable-arm-v7s: Add support for non-strict mode
- iommu/arm-smmu: Support non-strict mode
* ELAN900C:00 04F3:2844 touchscreen doesn't work (LP: #1811335)
- pinctrl: cannonlake: Fix community ordering for H variant
- pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant
* Add Cavium ThunderX2 SoC UNCORE PMU driver (LP: #1811200)
- perf: Export perf_event_update_userpage
- Documentation: perf: Add documentation for ThunderX2 PMU uncore driver
- drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
- [Config] New config CONFIG_THUNDERX2_PMU=m
* Update hisilicon SoC-specific drivers (LP: #1810457)
- SAUCE: Revert "net: hns3: Updates RX packet info fetch in case of multi
BD"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: separate roce from nic when
resetting"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Use roce handle when calling
roce
callback function"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add calling roce callback
function when link status change"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: optimize the process of
notifying
roce client"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add pf reset for hip08 RoCE"
- scsi: hisi_sas: Remove depends on HAS_DMA in case of platform dependency
- ethernet: hisilicon: hns: hns_dsaf_mac: Use generic eth_broadcast_addr
- scsi: hisi_sas: consolidate command check in hisi_sas_get_ata_protocol()
- scsi: hisi_sas: remove some unneeded structure members
- scsi: hisi_sas: Introduce hisi_sas_phy_set_linkrate()
- net: hns: Fix the process of adding broadcast addresses to tcam
- net: hns3: remove redundant variable 'protocol'
- scsi: hisi_sas: Drop hisi_sas_slot_abort()
- net: hns: Make many functions static
- net: hns: make hns_dsaf_roce_reset non static
- net: hisilicon: hns: Replace mdelay() with msleep()
- net: hns3: fix return value error while hclge_cmd_csq_clean failed
- net: hns: remove redundant variables 'max_frm' and 'tmp_mac_key'
- net: hns: Mark expected switch fall-through
- net: hns3: Mark expected switch fall-through
- net: hns3: Remove tx ring BD len register in hns3_enet
- net: hns: modify variable type in hns_nic_reuse_page
- net: hns: use eth_get_headlen interface instead of hns_nic_get_headlen
- net: hns3: modify variable type in hns3_nic_reuse_page
- net: hns3: Fix for vf vlan delete failed problem
- net: hns3: Fix for multicast failure
- net: hns3: Fix error of checking used vlan id
- net: hns3: Implement shutdown ops in hns3 pci driver
- net: hns3: Fix for loopback selftest failed problem
- net: hns3: Fix ping exited problem when doing lp selftest
- net: hns3: Preserve vlan 0 in hardware table
- net: hns3: Only update mac configuation when necessary
- net: hns3: Change the dst mac addr of loopback packet
- net: hns3: Remove redundant codes of query
[Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
Passed with Bionic SRU. startup='Tue Jan 15 13:44:04 2019' tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0' tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts='' mke2fs 1.44.1 (24-Mar-2018) tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s fanotify10.c:233: INFO: Test #0: ignore mount events created on a specific file fanotify10.c:221: PASS: group 0 got event: mask 20 pid=13198 fd=30 fanotify10.c:221: PASS: group 1 got event: mask 20 pid=13198 fd=30 fanotify10.c:221: PASS: group 2 got event: mask 20 pid=13198 fd=30 fanotify10.c:299: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:299: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:299: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:299: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:299: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:299: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event fanotify10.c:233: INFO: Test #1: don't ignore mount events created on another file fanotify10.c:221: PASS: group 0 got event: mask 20 pid=13198 fd=30 fanotify10.c:221: PASS: group 1 got event: mask 20 pid=13198 fd=30 fanotify10.c:221: PASS: group 2 got event: mask 20 pid=13198 fd=30 fanotify10.c:221: PASS: group 0 got event: mask 20 pid=13198 fd=30 fanotify10.c:221: PASS: group 1 got event: mask 20 pid=13198 fd=30 fanotify10.c:221: PASS: group 2 got event: mask 20 pid=13198 fd=30 fanotify10.c:221: PASS: group 0 got event: mask 20 pid=13198 fd=30 fanotify10.c:221: PASS: group 1 got event: mask 20 pid=13198 fd=30 fanotify10.c:221: PASS: group 2 got event: mask 20 pid=13198 fd=30 fanotify10.c:233: INFO: Test #2: ignore inode events created on a specific mount point fanotify10.c:221: PASS: group 0 got event: mask 20 pid=13198 fd=30 fanotify10.c:221: PASS: group 1 got event: mask 20 pid=13198 fd=30 fanotify10.c:221: PASS: group 2 got event: mask 20 pid=13198 fd=30 fanotify10.c:299: PASS: group 0 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got no event fanotify10.c:299: PASS: group 1 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got no event fanotify10.c:299: PASS: group 2 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got no event fanotify10.c:299: PASS: group 0 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got no event fanotify10.c:299: PASS: group 1 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got no event fanotify10.c:299: PASS: group 2 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got no event fanotify10.c:233: INFO: Test #3: don't ignore inode events created on another mount point fanotify10.c:221: PASS: group 0 got event: mask 20 pid=13198 fd=30 fanotify10.c:221: PASS: group 1 got event: mask 20 pid=13198 fd=30 fanotify10.c:221: PASS: group 2 got event: mask 20 pid=13198 fd=30 fanotify10.c:221: PASS: group 0 got event: mask 20 pid=13198 fd=30 fanotify10.c:221: PASS: group 1 got event: mask 20 pid=13198 fd=30 fanotify10.c:221: PASS: group 2 got event: mask 20 pid=13198 fd=30 fanotify10.c:221: PASS: group 0 got event: mask 20 pid=13198 fd=30 fanotify10.c:221: PASS: group 1 got event: mask 20 pid=13198 fd=30 fanotify10.c:221: PASS: group 2 got event: mask 20 pid=13198 fd=30 fanotify10.c:233: INFO: Test #4: ignore fs events created on a specific file fanotify10.c:162: CONF: FAN_MARK_FILESYSTEM not supported in kernel? fanotify10.c:233: INFO: Test #5: don't ignore mount events created on another file fanotify10.c:162: CONF: FAN_MARK_FILESYSTEM not supported in kernel? fanotify10.c:233: INFO: Test #6: ignore fs events created on a specific mount point fanotify10.c:162: CONF: FAN_MARK_FILESYSTEM not supported in kernel? fanotify10.c:233: INFO: Test #7: don't ignore fs events created on another mount point fanotify10.c:162: CONF: FAN_MARK_FILESYSTEM not supported in kernel? Summary: passed 36 failed 0 skipped 4 warnings 0 tag=fanotify10 stime=1547559844 dur=1 exit=exited stat=0 core=no cu=0 cs=0 ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802454 Title: fanotify10 in ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802454 Title: fanotify10 in ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802454 Title: fanotify10 in ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802454 Title: fanotify10 in ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
** Description changed:
== Justification ==
Commit 92183a42898d ("fsnotify: fix ignore mask logic in
send_to_group()") acknowledges the use case of ignoring an event on
an inode mark, because of an ignore mask on a mount mark of the same
group (i.e. I want to get all events on this file, except for the events
that came from that mount).
This change depends on correctly merging the inode marks and mount marks
group lists, so that the mount mark ignore mask would be tested in
send_to_group(). Alas, the merging of the lists did not take into
account the case where event in question is not in the mask of any of
the mount marks.
To fix this, completely remove the tests for inode and mount event masks
from the lists merging code.
== Fix ==
9bdda4e9 (fsnotify: fix ignore mask logic in fsnotify())
Test kernels for Bionic can be found here:
http://people.canonical.com/~phlin/kernel/lp-1802454-fanotify10/bionic/
- It seems that T/X poses with the same issue and the patch can be backported
- with the same logic, but I think we should target Bionic as it's a fix for
+ It seems that T/X poses with the same issue and we might be able to backport
+ it with the same logic, but I think we should target Bionic as it's a fix for
for 92183a42898d which was only applied to Bionic.
== Regression Potential ==
Low.
The backport work is required as it's missing commit 47d9c7cc457 in Bionic,
which generalizes the iteration of marks for inode_mark and vfsmount_mark,
from:
- iter_info.inode_mark
+ iter_info.inode_mark
to:
- iter_info.marks[FSNOTIFY_OBJ_TYPE_INODE]
+ iter_info.marks[FSNOTIFY_OBJ_TYPE_INODE]
But the patch can still be backported with the same logic without this
commit.
The test with the syscalls test in LTP test suite shows no sign of
regression.
== Test Case ==
Run the fanotify10 test in ubuntu_ltp_syscalls test suite. And it will pass
with the patched kernel.
Full LTP syscalls test with 4.15.0-42 in -proposed:
http://paste.ubuntu.com/p/Wm8nQ932g6/
Full LTP syscalls test with patched 4.15.0-42:
http://paste.ubuntu.com/p/nv4jW6shpJ/
-
This is a new test case that landed 7 days ago.
<<>>
tag=fanotify10 stime=1541744937
cmdline="fanotify10"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop1'
tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ext2 opts='' extra opts=''
mke2fs 1.44.1 (24-Mar-2018)
tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
fanotify10.c:199: INFO: Test #0: ignore mount events created on a specific
file
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:264: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:199: INFO: Test #1: don't ignore mount events created on another
file
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:199: INFO: Test #2: ignore inode events created on a specific
mount point
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:258: FAIL: group 0 (prio 1) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
fanotify10.c:258: FAIL: group 1 (prio 1) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
fanotify10.c:258: FAIL: group 2 (prio 1) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
fanotify10.c:258: FAIL: group 0 (prio 2) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
fanotify10.c:258: FAIL: group 1 (prio 2) with
[Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
** Description changed:
== Justification ==
Commit 92183a42898d ("fsnotify: fix ignore mask logic in
send_to_group()") acknowledges the use case of ignoring an event on
an inode mark, because of an ignore mask on a mount mark of the same
group (i.e. I want to get all events on this file, except for the events
that came from that mount).
This change depends on correctly merging the inode marks and mount marks
group lists, so that the mount mark ignore mask would be tested in
send_to_group(). Alas, the merging of the lists did not take into
account the case where event in question is not in the mask of any of
the mount marks.
To fix this, completely remove the tests for inode and mount event masks
from the lists merging code.
== Fix ==
9bdda4e9 (fsnotify: fix ignore mask logic in fsnotify())
Test kernels for Bionic can be found here:
http://people.canonical.com/~phlin/kernel/lp-1802454-fanotify10/bionic/
- It seems that T/X poses with the same issue and the patch can be
- backported with the same logic, but we should target Bionic only as it's
- a fix for 92183a42898d which was only applied to Bionic.
+ It seems that T/X poses with the same issue and the patch can be backported
+ with the same logic, but I think we should target Bionic as it's a fix for
+ for 92183a42898d which was only applied to Bionic.
== Regression Potential ==
Low.
- The backport work is required because it's missing another patch 47d9c7cc457
in Bionic, which generalizes the iteration of marks for inode_mark and
vfsmount_mark, from:
+ The backport work is required as it's missing commit 47d9c7cc457 in Bionic,
+ which generalizes the iteration of marks for inode_mark and vfsmount_mark,
from:
iter_info.inode_mark
to:
iter_info.marks[FSNOTIFY_OBJ_TYPE_INODE]
- But the patch can still be backported with the same logic.
+ But the patch can still be backported with the same logic without this
+ commit.
+
+ The test with the syscalls test in LTP test suite shows no sign of
+ regression.
== Test Case ==
- Run the fanotify10 test in ubuntu_ltp_syscalls test suite. And it will pass
with the patched kernel.
+ Run the fanotify10 test in ubuntu_ltp_syscalls test suite. And it will pass
+ with the patched kernel.
- Full LTP syscalls test with 4.15.0-42 in -proposed:
+ Full LTP syscalls test with 4.15.0-42 in -proposed:
http://paste.ubuntu.com/p/Wm8nQ932g6/
Full LTP syscalls test with patched 4.15.0-42:
http://paste.ubuntu.com/p/nv4jW6shpJ/
-
-
-
This is a new test case that landed 7 days ago.
<<>>
tag=fanotify10 stime=1541744937
cmdline="fanotify10"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop1'
tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ext2 opts='' extra opts=''
mke2fs 1.44.1 (24-Mar-2018)
tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
fanotify10.c:199: INFO: Test #0: ignore mount events created on a specific
file
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:264: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:199: INFO: Test #1: don't ignore mount events created on another
file
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:199: INFO: Test #2: ignore inode events created on a specific
mount point
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:258: FAIL: group 0 (prio 1) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
[Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
** Description changed:
+ == Justification ==
+ Commit 92183a42898d ("fsnotify: fix ignore mask logic in
+ send_to_group()") acknowledges the use case of ignoring an event on
+ an inode mark, because of an ignore mask on a mount mark of the same
+ group (i.e. I want to get all events on this file, except for the events
+ that came from that mount).
+
+ This change depends on correctly merging the inode marks and mount marks
+ group lists, so that the mount mark ignore mask would be tested in
+ send_to_group(). Alas, the merging of the lists did not take into
+ account the case where event in question is not in the mask of any of
+ the mount marks.
+
+ To fix this, completely remove the tests for inode and mount event masks
+ from the lists merging code.
+
+ == Fix ==
+ 9bdda4e9 (fsnotify: fix ignore mask logic in fsnotify())
+
+ Test kernels for Bionic can be found here:
+ http://people.canonical.com/~phlin/kernel/lp-1802454-fanotify10/bionic/
+
+ It seems that T/X poses with the same issue and the patch can be
+ backported with the same logic, but we should target Bionic only as it's
+ a fix for 92183a42898d which was only applied to Bionic.
+
+ == Regression Potential ==
+ Low.
+
+ The backport work is required because it's missing another patch 47d9c7cc457
in Bionic, which generalizes the iteration of marks for inode_mark and
vfsmount_mark, from:
+ iter_info.inode_mark
+ to:
+ iter_info.marks[FSNOTIFY_OBJ_TYPE_INODE]
+
+ But the patch can still be backported with the same logic.
+
+ == Test Case ==
+ Run the fanotify10 test in ubuntu_ltp_syscalls test suite. And it will pass
with the patched kernel.
+
+ Full LTP syscalls test with 4.15.0-42 in -proposed:
+ http://paste.ubuntu.com/p/Wm8nQ932g6/
+
+ Full LTP syscalls test with patched 4.15.0-42:
+ http://paste.ubuntu.com/p/nv4jW6shpJ/
+
+
+ -
+
+
This is a new test case that landed 7 days ago.
<<>>
tag=fanotify10 stime=1541744937
cmdline="fanotify10"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop1'
tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ext2 opts='' extra opts=''
mke2fs 1.44.1 (24-Mar-2018)
tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
fanotify10.c:199: INFO: Test #0: ignore mount events created on a specific
file
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:264: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:199: INFO: Test #1: don't ignore mount events created on another
file
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:199: INFO: Test #2: ignore inode events created on a specific
mount point
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:258: FAIL: group 0 (prio 1) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
fanotify10.c:258: FAIL: group 1 (prio 1) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
fanotify10.c:258: FAIL: group 2 (prio 1) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
fanotify10.c:258: FAIL: group 0 (prio 2) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
fanotify10.c:258: FAIL: group 1 (prio 2) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
fanotify10.c:258: FAIL: group 2 (prio 2) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
fanotify10.c:199: INFO: Test #3: don't ignore inode events created on another
mount point
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
[Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
For cosmic, it's been fixed in stable update, bug 1801931 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802454 Title: fanotify10 in ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
LTP syscalls full test on Bionic (with patched 4.15.0-39-generic kernel) http://paste.ubuntu.com/p/m7DXXHYX9K/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802454 Title: fanotify10 in ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Tags added: cosmic trusty xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802454 Title: fanotify10 in ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
Can be reproduced on different kernels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802454 Title: fanotify10 in ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
