This also occurs in 4.15.0-1012-kvm so it is NOT a regression. Config has:
# CONFIG_DNOTIFY is not set so the failure is because DNOTIFY has be disables, which I believe is an issue, this functionality should be enabled IMHO. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1782723 Title: dnotify in ubuntu_stress_smoke_test failed on B-KVM Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in stress-ng package in Ubuntu: New Bug description: This issue does not exist in 4.15.0-1015.15 - kvm 08:08:02 DEBUG| [stdout] dnotify FAILED 08:08:02 DEBUG| [stdout] stress-ng: debug: [3043] 2 processors online, 2 processors configured 08:08:02 DEBUG| [stdout] stress-ng: info: [3043] dispatching hogs: 4 dnotify 08:08:02 DEBUG| [stdout] stress-ng: debug: [3043] cache allocate: reducing cache level from L3 (too high) to L2 08:08:02 DEBUG| [stdout] stress-ng: debug: [3043] cache allocate: default cache size: 4096K 08:08:02 DEBUG| [stdout] stress-ng: debug: [3043] starting stressors 08:08:02 DEBUG| [stdout] stress-ng: debug: [3044] stress-ng-dnotify: started [3044] (instance 0) 08:08:02 DEBUG| [stdout] stress-ng: debug: [3043] 4 stressors spawned 08:08:02 DEBUG| [stdout] stress-ng: fail: [3044] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument) 08:08:02 DEBUG| [stdout] stress-ng: debug: [3046] stress-ng-dnotify: started [3046] (instance 2) 08:08:02 DEBUG| [stdout] stress-ng: debug: [3047] stress-ng-dnotify: started [3047] (instance 3) 08:08:02 DEBUG| [stdout] stress-ng: fail: [3044] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument) 08:08:02 DEBUG| [stdout] stress-ng: fail: [3046] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument) 08:08:02 DEBUG| [stdout] stress-ng: fail: [3044] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument) 08:08:02 DEBUG| [stdout] stress-ng: fail: [3046] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument) 08:08:02 DEBUG| [stdout] stress-ng: fail: [3046] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument) 08:08:02 DEBUG| [stdout] stress-ng: fail: [3046] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument) 08:08:02 DEBUG| [stdout] stress-ng: fail: [3046] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument) 08:08:02 DEBUG| [stdout] info: 5 failures reached, aborting stress process 08:08:02 DEBUG| [stdout] stress-ng: debug: [3046] stress-ng-dnotify: exited [3046] (instance 2) 08:08:02 DEBUG| [stdout] stress-ng: fail: [3047] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument) 08:08:02 DEBUG| [stdout] stress-ng: fail: [3047] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument) 08:08:02 DEBUG| [stdout] stress-ng: fail: [3047] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument) 08:08:02 DEBUG| [stdout] stress-ng: fail: [3047] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument) 08:08:02 DEBUG| [stdout] stress-ng: fail: [3047] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument) 08:08:02 DEBUG| [stdout] info: 5 failures reached, aborting stress process 08:08:02 DEBUG| [stdout] stress-ng: debug: [3047] stress-ng-dnotify: exited [3047] (instance 3) 08:08:02 DEBUG| [stdout] stress-ng: fail: [3044] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument) 08:08:02 DEBUG| [stdout] stress-ng: fail: [3044] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument) 08:08:02 DEBUG| [stdout] info: 5 failures reached, aborting stress process 08:08:02 DEBUG| [stdout] stress-ng: debug: [3044] stress-ng-dnotify: exited [3044] (instance 0) 08:08:02 DEBUG| [stdout] stress-ng: error: [3043] process 3044 (stress-ng-dnotify) terminated with an error, exit status=1 (stress-ng core failure) 08:08:02 DEBUG| [stdout] stress-ng: debug: [3043] process [3044] terminated 08:08:02 DEBUG| [stdout] stress-ng: debug: [3045] stress-ng-dnotify: started [3045] (instance 1) 08:08:02 DEBUG| [stdout] stress-ng: fail: [3045] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument) 08:08:02 DEBUG| [stdout] stress-ng: fail: [3045] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument) 08:08:02 DEBUG| [stdout] stress-ng: fail: [3045] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument) 08:08:02 DEBUG| [stdout] stress-ng: fail: [3045] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument) 08:08:02 DEBUG| [stdout] stress-ng: fail: [3045] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument) 08:08:02 DEBUG| [stdout] info: 5 failures reached, aborting stress process 08:08:02 DEBUG| [stdout] stress-ng: debug: [3045] stress-ng-dnotify: exited [3045] (instance 1) 08:08:02 DEBUG| [stdout] stress-ng: error: [3043] process 3045 (stress-ng-dnotify) terminated with an error, exit status=1 (stress-ng core failure) 08:08:02 DEBUG| [stdout] stress-ng: debug: [3043] process [3045] terminated 08:08:02 DEBUG| [stdout] stress-ng: error: [3043] process 3046 (stress-ng-dnotify) terminated with an error, exit status=1 (stress-ng core failure) 08:08:02 DEBUG| [stdout] stress-ng: debug: [3043] process [3046] terminated 08:08:02 DEBUG| [stdout] stress-ng: error: [3043] process 3047 (stress-ng-dnotify) terminated with an error, exit status=1 (stress-ng core failure) 08:08:02 DEBUG| [stdout] stress-ng: debug: [3043] process [3047] terminated 08:08:02 DEBUG| [stdout] stress-ng: info: [3043] unsuccessful run completed in 0.01s 08:08:02 DEBUG| [stdout] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1016-kvm 4.15.0-1016.16 ProcVersionSignature: User Name 4.15.0-1016.16-kvm 4.15.18 Uname: Linux 4.15.0-1016-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Fri Jul 20 08:11:19 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1782723/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
