dnotify in ubuntu_stress_smoke_test failed on KVM kernels

Bug #1782723 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Fix Released
Undecided
Po-Hsu Lin
linux-kvm (Ubuntu)
Won't Fix
Undecided
Po-Hsu Lin
Nominated for Bionic by Po-Hsu Lin
Nominated for Xenial by Po-Hsu Lin

Bug Description

== Justification ==
In the Xenial 4.4 and Bionic 4.15 KVM kernel, the CONFIG_DNOTIFY was not set, which is causing failures in the stress-ng dnotify test.

 [stdout] dnotify FAILED
 [stdout] stress-ng: debug: [3043] 2 processors online, 2 processors configured
 [stdout] stress-ng: info: [3043] dispatching hogs: 4 dnotify
 [stdout] stress-ng: debug: [3043] cache allocate: reducing cache level from L3 (too high) to L2
 [stdout] stress-ng: debug: [3043] cache allocate: default cache size: 4096K
 [stdout] stress-ng: debug: [3043] starting stressors
 [stdout] stress-ng: debug: [3044] stress-ng-dnotify: started [3044] (instance 0)
 [stdout] stress-ng: debug: [3043] 4 stressors spawned
 [stdout] stress-ng: fail: [3044] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument)
 [stdout] stress-ng: debug: [3046] stress-ng-dnotify: started [3046] (instance 2)
 [stdout] stress-ng: debug: [3047] stress-ng-dnotify: started [3047] (instance 3)
 [stdout] stress-ng: fail: [3044] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument)
 [stdout] stress-ng: fail: [3046] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument)
 [stdout] stress-ng: fail: [3044] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument)
 [stdout] stress-ng: fail: [3046] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument)
 [stdout] stress-ng: fail: [3046] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument)
 [stdout] stress-ng: fail: [3046] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument)
 [stdout] stress-ng: fail: [3046] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument)
 [stdout] info: 5 failures reached, aborting stress process
 [stdout] stress-ng: debug: [3046] stress-ng-dnotify: exited [3046] (instance 2)
 [stdout] stress-ng: fail: [3047] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument)
 [stdout] stress-ng: fail: [3047] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument)
 [stdout] stress-ng: fail: [3047] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument)
 [stdout] stress-ng: fail: [3047] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument)
 [stdout] stress-ng: fail: [3047] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument)
 [stdout] info: 5 failures reached, aborting stress process
 [stdout] stress-ng: debug: [3047] stress-ng-dnotify: exited [3047] (instance 3)
 [stdout] stress-ng: fail: [3044] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument)
 [stdout] stress-ng: fail: [3044] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument)
 [stdout] info: 5 failures reached, aborting stress process
 [stdout] stress-ng: debug: [3044] stress-ng-dnotify: exited [3044] (instance 0)
 [stdout] stress-ng: error: [3043] process 3044 (stress-ng-dnotify) terminated with an error, exit status=1 (stress-ng core failure)
 [stdout] stress-ng: debug: [3043] process [3044] terminated
 [stdout] stress-ng: debug: [3045] stress-ng-dnotify: started [3045] (instance 1)
 [stdout] stress-ng: fail: [3045] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument)
 [stdout] stress-ng: fail: [3045] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument)
 [stdout] stress-ng: fail: [3045] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument)
 [stdout] stress-ng: fail: [3045] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument)
 [stdout] stress-ng: fail: [3045] stress-ng-dnotify: fcntl F_NOTIFY failed, errno=22 (Invalid argument)
 [stdout] info: 5 failures reached, aborting stress process
 [stdout] stress-ng: debug: [3045] stress-ng-dnotify: exited [3045] (instance 1)
 [stdout] stress-ng: error: [3043] process 3045 (stress-ng-dnotify) terminated with an error, exit status=1 (stress-ng core failure)
 [stdout] stress-ng: debug: [3043] process [3045] terminated
 [stdout] stress-ng: error: [3043] process 3046 (stress-ng-dnotify) terminated with an error, exit status=1 (stress-ng core failure)
 [stdout] stress-ng: debug: [3043] process [3046] terminated
 [stdout] stress-ng: error: [3043] process 3047 (stress-ng-dnotify) terminated with an error, exit status=1 (stress-ng core failure)
 [stdout] stress-ng: debug: [3043] process [3047] terminated
 [stdout] stress-ng: info: [3043] unsuccessful run completed in 0.01s

== Fix ==
UBUNTU: kvm: [Config] enable CONFIG_DNOTIFY

== Test ==
The dnotify test in stress-ng will pass with this patch applied.
Test kernel could be found here:
http://people.canonical.com/~phlin/kernel/lp-1782723-dnotify/

== Regression Potential ==
Minimal.
No code changes, just a config change.

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)

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Colin Ian King (colin-king) wrote :

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.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Affecting X-KVM as well.

summary: - dnotify in ubuntu_stress_smoke_test failed on B-KVM
+ dnotify in ubuntu_stress_smoke_test failed on KVM kernels
tags: added: xenial
Po-Hsu Lin (cypressyew)
Changed in ubuntu-kernel-tests:
assignee: nobody → Po-Hsu Lin (cypressyew)
Changed in linux-kvm (Ubuntu):
assignee: nobody → Po-Hsu Lin (cypressyew)
no longer affects: stress-ng (Ubuntu)
Changed in ubuntu-kernel-tests:
status: New → In Progress
Changed in linux-kvm (Ubuntu):
status: New → In Progress
Po-Hsu Lin (cypressyew)
description: updated
Po-Hsu Lin (cypressyew)
Changed in linux-kvm (Ubuntu):
status: In Progress → Won't Fix
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Task for Linux set to won't fix as per Kamal's comment[1]:
    Since dnotify has been obsolete for many years now, we would prefer not
to enable it in linux-kvm (if its only for the purpose of stress-ng
testing).

This will be addressed in the test suite instead.

[1] https://lists.ubuntu.com/archives/kernel-team/2018-August/094737.html

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Changed in ubuntu-kernel-tests:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.