| Message ID | 20180816025622.8200-2-po-hsu.lin@canonical.com |
|---|---|
| State | New |
| Headers | show |
| Series | UBUNTU: kvm: [Config] enable CONFIG_DNOTIFY | expand |
diff --git a/debian.kvm/config/config.common.ubuntu b/debian.kvm/config/config.common.ubuntu index 2356d44..eeb6fe5 100644 --- a/debian.kvm/config/config.common.ubuntu +++ b/debian.kvm/config/config.common.ubuntu @@ -579,7 +579,7 @@ CONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=y # CONFIG_DM_UEVENT is not set # CONFIG_DM_VERITY is not set # CONFIG_DM_ZERO is not set -# CONFIG_DNOTIFY is not set +CONFIG_DNOTIFY=y CONFIG_DNS_RESOLVER=m # CONFIG_DOUBLEFAULT is not set CONFIG_DQL=y
BugLink: https://bugs.launchpad.net/bugs/1782723 Adding CONFIG_DNOTIFY=y to common config. It's better to enable this config in KVM kenrels not only because it is required for the dnotify test in stress-ng, the config description also suggest that some applications may still rely on it. Signed-off-by: Po-Hsu Lin <po-hsu.lin@canonical.com> --- debian.kvm/config/config.common.ubuntu | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)