** Description changed: - This is a new test for overlayfs: + == SRU Justification == + fanotify06 test from ubuntu_ltp_syscalls reported that test #1 for overlayfs has received more than one expected event: + <<<test_start>>> tag=fanotify06 stime=1560747299 cmdline="fanotify06" contacts="" analysis=exit <<<test_output>>> incrementing stop tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2' tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1112: INFO: Timeout per run is 0h 05m 00s fanotify06.c:169: INFO: Test #0: Fanotify merge mount mark fanotify06.c:147: PASS: group 0 got event: mask 2 pid=1136 fd=15 - fanotify06.c:147: PASS: group 1 got event: mask 2 pid=1136 fd=15 - fanotify06.c:147: PASS: group 2 got event: mask 2 pid=1136 fd=15 - fanotify06.c:230: PASS: group 3 got no event - fanotify06.c:230: PASS: group 4 got no event - fanotify06.c:230: PASS: group 5 got no event - fanotify06.c:230: PASS: group 6 got no event - fanotify06.c:230: PASS: group 7 got no event + .... fanotify06.c:230: PASS: group 8 got no event fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark fanotify06.c:208: FAIL: group 0 got more than one event (48 > 24) fanotify06.c:208: FAIL: group 1 got more than one event (48 > 24) fanotify06.c:208: FAIL: group 2 got more than one event (48 > 24) fanotify06.c:220: FAIL: group 3 got event fanotify06.c:220: FAIL: group 4 got event fanotify06.c:220: FAIL: group 5 got event fanotify06.c:220: FAIL: group 6 got event fanotify06.c:220: FAIL: group 7 got event fanotify06.c:220: FAIL: group 8 got event Summary: passed 9 failed 9 skipped 0 warnings 0 <<<execution_status>>> initiation_status="ok" duration=3 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=1 <<<test_end>>> + This duplicated event was generated with operations on files with "fake" + path. + + == Fix == + * d9899030 (ovl: do not generate duplicate fsnotify events for "fake" path) + + This patch can be cherry-picked into Disco. + + For older kernels, they are not affected by this issue (without commit + d1d04ef8) + + == Test == + Test kernel could be found here: + https://people.canonical.com/~phlin/kernel/lp-1833028-fanotify06-ovl/ + + Verified on a KVM node, the fanotify06 test will pass with this patched kernel: + fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark + fanotify06.c:147: PASS: group 0 got event: mask 2 pid=5997 fd=30 + fanotify06.c:147: PASS: group 1 got event: mask 2 pid=5997 fd=30 + fanotify06.c:147: PASS: group 2 got event: mask 2 pid=5997 fd=30 + fanotify06.c:230: PASS: group 3 got no event + fanotify06.c:230: PASS: group 4 got no event + fanotify06.c:230: PASS: group 5 got no event + fanotify06.c:230: PASS: group 6 got no event + fanotify06.c:230: PASS: group 7 got no event + fanotify06.c:230: PASS: group 8 got no event + + == Regression Potential == + Low, fix limited to overlayfs and just corrects the flag behaviour with "fake" path. + + ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: User Name 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 AlsaDevices: - total 0 - crw-rw---- 1 root audio 116, 1 Jun 17 04:37 seq - crw-rw---- 1 root audio 116, 33 Jun 17 04:37 timer + total 0 + crw-rw---- 1 root audio 116, 1 Jun 17 04:37 seq + crw-rw---- 1 root audio 116, 33 Jun 17 04:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: - + Date: Mon Jun 17 04:40:18 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: - + ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro RelatedPackageVersions: - linux-restricted-modules-5.0.0-16-generic N/A - linux-backports-modules-5.0.0-16-generic N/A - linux-firmware 1.178.1 + linux-restricted-modules-5.0.0-16-generic N/A + linux-backports-modules-5.0.0-16-generic N/A + linux-firmware 1.178.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833028 Title: fanotify06 from ubuntu_ltp_syscalls failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1833028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
