[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
** Changed in: ubuntu-kernel-tests
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
Fix Released
Status in linux-aws package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-kvm package in Ubuntu:
Fix Released
Status in linux-aws source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-kvm source package in Cosmic:
Fix Released
Status in linux-aws source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-kvm source package in Disco:
Fix Released
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 2019
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/1812624/+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
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
This bug was fixed in the package linux-kvm - 5.0.0-1011.12 --- linux-kvm (5.0.0-1011.12) disco; urgency=medium * linux-kvm: 5.0.0-1011.12 -proposed tracker (LP: #1834892) * q-r-t security test wants SCHED_STACK_END_CHECK to be enabled in KVM kernels (LP: #1812159) - [Config]: enable SCHED_STACK_END_CHECK * PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM (LP: #1812624) - [Config]: enable PAGE_POISONING, PAGE_POISONING_NO_SANITY, PAGE_POISONING_ZERO * test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on B/C/D KVM (LP: #1811981) - [Config]: enable CONFIG_LOCK_DOWN_KERNEL [ Ubuntu: 5.0.0-21.22 ] * linux: 5.0.0-21.22 -proposed tracker (LP: #1834902) * Disco update: 5.0.15 upstream stable release (LP: #1834529) - net: stmmac: Use bfsize1 in ndesc_init_rx_desc - Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup() - ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings - staging: greybus: power_supply: fix prop-descriptor request size - staging: wilc1000: Avoid GFP_KERNEL allocation from atomic context. - staging: most: cdev: fix chrdev_region leak in mod_exit - staging: most: sound: pass correct device when creating a sound card - ASoC: tlv320aic3x: fix reset gpio reference counting - ASoC: hdmi-codec: fix S/PDIF DAI - ASoC: stm32: sai: fix iec958 controls indexation - ASoC: stm32: sai: fix exposed capabilities in spdif mode - ASoC: stm32: sai: fix race condition in irq handler - ASoC:soc-pcm:fix a codec fixup issue in TDM case - ASoC:hdac_hda:use correct format to setup hda codec - ASoC:intel:skl:fix a simultaneous playback & capture issue on hda platform - ASoC: dpcm: prevent snd_soc_dpcm use after free - ASoC: nau8824: fix the issue of the widget with prefix name - ASoC: nau8810: fix the issue of widget with prefixed name - ASoC: samsung: odroid: Fix clock configuration for 44100 sample rate - ASoC: rt5682: Check JD status when system resume - ASoC: rt5682: fix jack type detection issue - ASoC: rt5682: recording has no sound after booting - ASoC: wm_adsp: Add locking to wm_adsp2_bus_error - clk: meson-gxbb: round the vdec dividers to closest - ASoC: stm32: dfsdm: manage multiple prepare - ASoC: stm32: dfsdm: fix debugfs warnings on entry creation - ASoC: cs4270: Set auto-increment bit for register writes - ASoC: dapm: Fix NULL pointer dereference in snd_soc_dapm_free_kcontrol - drm/omap: hdmi4_cec: Fix CEC clock handling for PM - IB/hfi1: Clear the IOWAIT pending bits when QP is put into error state - IB/hfi1: Eliminate opcode tests on mr deref - IB/hfi1: Fix the allocation of RSM table - MIPS: KGDB: fix kgdb support for SMP platforms. - ASoC: tlv320aic32x4: Fix Common Pins - drm/mediatek: Fix an error code in mtk_hdmi_dt_parse_pdata() - perf/x86/intel: Fix handling of wakeup_events for multi-entry PEBS - perf/x86/intel: Initialize TFA MSR - linux/kernel.h: Use parentheses around argument in u64_to_user_ptr() - iov_iter: Fix build error without CONFIG_CRYPTO - xtensa: fix initialization of pt_regs::syscall in start_thread - ASoC: rockchip: pdm: fix regmap_ops hang issue - drm/amdkfd: Add picasso pci id - drm/amdgpu: Adjust IB test timeout for XGMI configuration - drm/amdgpu: amdgpu_device_recover_vram always failed if only one node in shadow_list - drm/amd/display: fix cursor black issue - ASoC: cs35l35: Disable regulators on driver removal - objtool: Add rewind_stack_do_exit() to the noreturn list - slab: fix a crash by reading /proc/slab_allocators - drm/sun4i: tcon top: Fix NULL/invalid pointer dereference in sun8i_tcon_top_un/bind - virtio_pci: fix a NULL pointer reference in vp_del_vqs - RDMA/vmw_pvrdma: Fix memory leak on pvrdma_pci_remove - RDMA/hns: Fix bug that caused srq creation to fail - KEYS: trusted: fix -Wvarags warning - scsi: csiostor: fix missing data copy in csio_scsi_err_handler() - drm/mediatek: fix possible object reference leak - drm/mediatek: fix the rate and divder of hdmi phy for MT2701 - drm/mediatek: make implementation of recalc_rate() for MT2701 hdmi phy - drm/mediatek: remove flag CLK_SET_RATE_PARENT for MT2701 hdmi phy - drm/mediatek: using new factor for tvdpll for MT2701 hdmi phy - drm/mediatek: no change parent rate in round_rate() for MT2701 hdmi phy - ASoC: Intel: kbl: fix wrong number of channels - ASoC: stm32: sai: fix master clock management - ALSA: hda: Fix racy display power access - virtio-blk: limit number of hw queues by nr_cpu_ids - blk-mq: introduce blk_mq_complete_request_sync() - nvme: cancel request synchronously - nvme-fc: correct csn initialization and increments on error - nvmet: fix discover log page when
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
This bug was fixed in the package linux-kvm - 5.0.0-1011.12 --- linux-kvm (5.0.0-1011.12) disco; urgency=medium * linux-kvm: 5.0.0-1011.12 -proposed tracker (LP: #1834892) * q-r-t security test wants SCHED_STACK_END_CHECK to be enabled in KVM kernels (LP: #1812159) - [Config]: enable SCHED_STACK_END_CHECK * PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM (LP: #1812624) - [Config]: enable PAGE_POISONING, PAGE_POISONING_NO_SANITY, PAGE_POISONING_ZERO * test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on B/C/D KVM (LP: #1811981) - [Config]: enable CONFIG_LOCK_DOWN_KERNEL [ Ubuntu: 5.0.0-21.22 ] * linux: 5.0.0-21.22 -proposed tracker (LP: #1834902) * Disco update: 5.0.15 upstream stable release (LP: #1834529) - net: stmmac: Use bfsize1 in ndesc_init_rx_desc - Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup() - ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings - staging: greybus: power_supply: fix prop-descriptor request size - staging: wilc1000: Avoid GFP_KERNEL allocation from atomic context. - staging: most: cdev: fix chrdev_region leak in mod_exit - staging: most: sound: pass correct device when creating a sound card - ASoC: tlv320aic3x: fix reset gpio reference counting - ASoC: hdmi-codec: fix S/PDIF DAI - ASoC: stm32: sai: fix iec958 controls indexation - ASoC: stm32: sai: fix exposed capabilities in spdif mode - ASoC: stm32: sai: fix race condition in irq handler - ASoC:soc-pcm:fix a codec fixup issue in TDM case - ASoC:hdac_hda:use correct format to setup hda codec - ASoC:intel:skl:fix a simultaneous playback & capture issue on hda platform - ASoC: dpcm: prevent snd_soc_dpcm use after free - ASoC: nau8824: fix the issue of the widget with prefix name - ASoC: nau8810: fix the issue of widget with prefixed name - ASoC: samsung: odroid: Fix clock configuration for 44100 sample rate - ASoC: rt5682: Check JD status when system resume - ASoC: rt5682: fix jack type detection issue - ASoC: rt5682: recording has no sound after booting - ASoC: wm_adsp: Add locking to wm_adsp2_bus_error - clk: meson-gxbb: round the vdec dividers to closest - ASoC: stm32: dfsdm: manage multiple prepare - ASoC: stm32: dfsdm: fix debugfs warnings on entry creation - ASoC: cs4270: Set auto-increment bit for register writes - ASoC: dapm: Fix NULL pointer dereference in snd_soc_dapm_free_kcontrol - drm/omap: hdmi4_cec: Fix CEC clock handling for PM - IB/hfi1: Clear the IOWAIT pending bits when QP is put into error state - IB/hfi1: Eliminate opcode tests on mr deref - IB/hfi1: Fix the allocation of RSM table - MIPS: KGDB: fix kgdb support for SMP platforms. - ASoC: tlv320aic32x4: Fix Common Pins - drm/mediatek: Fix an error code in mtk_hdmi_dt_parse_pdata() - perf/x86/intel: Fix handling of wakeup_events for multi-entry PEBS - perf/x86/intel: Initialize TFA MSR - linux/kernel.h: Use parentheses around argument in u64_to_user_ptr() - iov_iter: Fix build error without CONFIG_CRYPTO - xtensa: fix initialization of pt_regs::syscall in start_thread - ASoC: rockchip: pdm: fix regmap_ops hang issue - drm/amdkfd: Add picasso pci id - drm/amdgpu: Adjust IB test timeout for XGMI configuration - drm/amdgpu: amdgpu_device_recover_vram always failed if only one node in shadow_list - drm/amd/display: fix cursor black issue - ASoC: cs35l35: Disable regulators on driver removal - objtool: Add rewind_stack_do_exit() to the noreturn list - slab: fix a crash by reading /proc/slab_allocators - drm/sun4i: tcon top: Fix NULL/invalid pointer dereference in sun8i_tcon_top_un/bind - virtio_pci: fix a NULL pointer reference in vp_del_vqs - RDMA/vmw_pvrdma: Fix memory leak on pvrdma_pci_remove - RDMA/hns: Fix bug that caused srq creation to fail - KEYS: trusted: fix -Wvarags warning - scsi: csiostor: fix missing data copy in csio_scsi_err_handler() - drm/mediatek: fix possible object reference leak - drm/mediatek: fix the rate and divder of hdmi phy for MT2701 - drm/mediatek: make implementation of recalc_rate() for MT2701 hdmi phy - drm/mediatek: remove flag CLK_SET_RATE_PARENT for MT2701 hdmi phy - drm/mediatek: using new factor for tvdpll for MT2701 hdmi phy - drm/mediatek: no change parent rate in round_rate() for MT2701 hdmi phy - ASoC: Intel: kbl: fix wrong number of channels - ASoC: stm32: sai: fix master clock management - ALSA: hda: Fix racy display power access - virtio-blk: limit number of hw queues by nr_cpu_ids - blk-mq: introduce blk_mq_complete_request_sync() - nvme: cancel request synchronously - nvme-fc: correct csn initialization and increments on error - nvmet: fix discover log page when
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
I can confirm that the PAGE_POISONING, PAGE_POISONING_NO_SANITY, and
PAGE_POISONING_ZERO config options are set in the linux-kvm
5.0.0-1011.12 kernel in disco proposed. Thanks!
** Tags added: verification-done-disco
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
In Progress
Status in linux-aws package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-kvm package in Ubuntu:
In Progress
Status in linux-aws source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-kvm source package in Cosmic:
Fix Released
Status in linux-aws source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-kvm source package in Disco:
Fix Committed
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 2019
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/1812624/+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
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
** Changed in: linux-kvm (Ubuntu Disco)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
In Progress
Status in linux-aws package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-kvm package in Ubuntu:
In Progress
Status in linux-aws source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-kvm source package in Cosmic:
Fix Released
Status in linux-aws source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-kvm source package in Disco:
Fix Committed
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 2019
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/1812624/+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
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
For D/linux-kvm https://lists.ubuntu.com/archives/kernel-
team/2019-June/101294.html
** Tags added: disco
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
In Progress
Status in linux-aws package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-kvm package in Ubuntu:
In Progress
Status in linux-aws source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-kvm source package in Cosmic:
Fix Released
Status in linux-aws source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-kvm source package in Disco:
In Progress
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 2019
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/1812624/+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
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
This bug was fixed in the package linux-azure - 5.0.0-1002.2
---
linux-azure (5.0.0-1002.2) disco; urgency=medium
* linux-azure: 5.0.0-1002.2 -proposed tracker (LP: #1823220)
* Set CONFIG_RANDOM_TRUST_CPU=y (LP: #1823754)
- [Config] CONFIG_RANDOM_TRUST_CPU=y
* PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was
expected to be set in C-KVM (LP: #1812624)
- [Config]: enable PAGE_POISONING, PAGE_POISONING_NO_SANITY,
PAGE_POISONING_ZERO
* Add CONFIG_NO_HZ_FULL=y to linux-azure kernels (LP: #1818138)
- [Config] linux-azure: CONFIG_NO_HZ_FULL=y
* Miscellaneous Ubuntu changes
- [Config] update configs after rebase to 5.0.0-10.11
- Revert "UBUNTU: [Config] azure: CONFIG_HOTPLUG_CPU=n"
[ Ubuntu: 5.0.0-10.11 ]
* linux: 5.0.0-10.11 -proposed tracker (LP: #1823936)
* Apparmor enforcement failure in lxc selftests (LP: #1823379)
- SAUCE: apparmor: Restore Y/N in /sys for apparmor's "enabled"
* systemd cause kernel trace "BUG: unable to handle kernel paging request at
6db23a14" on Cosmic i386 (LP: #1813244)
- openvswitch: fix flow actions reallocation
[ Ubuntu: 5.0.0-9.10 ]
* linux: 5.0.0-9.10 -proposed tracker (LP: #1823228)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
- [Packaging] update helper scripts
- [Packaging] resync retpoline extraction
* Huawei Hi1822 NIC has poor performance (LP: #1820187)
- net-next/hinic: replace disable_irq_nosync/enable_irq
* Add uid shifting overlay filesystem (shiftfs) (LP: #1823186)
- shiftfs: uid/gid shifting bind mount
- shiftfs: rework and extend
- shiftfs: support some btrfs ioctls
- [Config] enable shiftfs
* Cannot boot or install - have to use nomodeset (LP: #1821820)
- Revert "drm/i915/fbdev: Actually configure untiled displays"
* Disco update: v5.0.6 upstream stable release (LP: #1823060)
- netfilter: nf_tables: fix set double-free in abort path
- dccp: do not use ipv6 header for ipv4 flow
- genetlink: Fix a memory leak on error path
- gtp: change NET_UDP_TUNNEL dependency to select
- ipv6: make ip6_create_rt_rcu return ip6_null_entry instead of NULL
- mac8390: Fix mmio access size probe
- mISDN: hfcpci: Test both vendor & device ID for Digium HFC4S
- net: aquantia: fix rx checksum offload for UDP/TCP over IPv6
- net: datagram: fix unbounded loop in __skb_try_recv_datagram()
- net/packet: Set __GFP_NOWARN upon allocation in alloc_pg_vec
- net: phy: meson-gxl: fix interrupt support
- net: rose: fix a possible stack overflow
- net: stmmac: fix memory corruption with large MTUs
- net-sysfs: call dev_hold if kobject_init_and_add success
- net: usb: aqc111: Extend HWID table by QNAP device
- packets: Always register packet sk in the same order
- rhashtable: Still do rehash when we get EEXIST
- sctp: get sctphdr by offset in sctp_compute_cksum
- sctp: use memdup_user instead of vmemdup_user
- tcp: do not use ipv6 header for ipv4 flow
- tipc: allow service ranges to be connect()'ed on RDM/DGRAM
- tipc: change to check tipc_own_id to return in tipc_net_stop
- tipc: fix cancellation of topology subscriptions
- tun: properly test for IFF_UP
- vrf: prevent adding upper devices
- vxlan: Don't call gro_cells_destroy() before device is unregistered
- thunderx: enable page recycling for non-XDP case
- thunderx: eliminate extra calls to put_page() for pages held for recycling
- net: dsa: mv88e6xxx: fix few issues in mv88e6390x_port_set_cmode
- net: mii: Fix PAUSE cap advertisement from linkmode_adv_to_lcl_adv_t()
helper
- net: phy: don't clear BMCR in genphy_soft_reset
- r8169: fix cable re-plugging issue
- ila: Fix rhashtable walker list corruption
- tun: add a missing rcu_read_unlock() in error path
- powerpc/fsl: Fix the flush of branch predictor.
- Btrfs: fix incorrect file size after shrinking truncate and fsync
- btrfs: remove WARN_ON in log_dir_items
- btrfs: don't report readahead errors and don't update statistics
- btrfs: Fix bound checking in qgroup_trace_new_subtree_blocks
- btrfs: Avoid possible qgroup_rsv_size overflow in
btrfs_calculate_inode_block_rsv_size
- Btrfs: fix assertion failure on fsync with NO_HOLES enabled
- locks: wake any locks blocked on request before deadlock check
- tracing: initialize variable in create_dyn_event()
- ARM: imx6q: cpuidle: fix bug that CPU might not wake up at expected time
- powerpc: bpf: Fix generation of load/store DW instructions
- vfio: ccw: only free cp on final interrupt
- NFS: Fix nfs4_lock_state refcounting in nfs4_alloc_{lock,unlock}data()
- NFS: fix mount/umount race in nlmclnt.
- NFSv4.1 don't free interrupted slot on open
- net: dsa: qca8k: remove leftover phy accessors
- ALSA: rawmidi: Fix potential Spectre v1 vulnerability
- ALSA: seq:
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
This bug was fixed in the package linux-kvm - 4.18.0-1009.9
---
linux-kvm (4.18.0-1009.9) cosmic; urgency=medium
* linux-kvm: 4.18.0-1009.9 -proposed tracker (LP: #1819621)
* CONFIG_SECURITY_SELINUX_DISABLE should be disabled on KVM kernel
(LP: #1812153)
- [Config]: disable CONFIG_SECURITY_SELINUX_DISABLE
- [Config]: disable CONFIG_SECURITY_WRITABLE_HOOKS
* PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was
expected to be set in C-KVM (LP: #1812624)
- [Config]: enable PAGE_POISONING, PAGE_POISONING_NO_SANITY,
PAGE_POISONING_ZERO
[ Ubuntu: 4.18.0-17.18 ]
* linux: 4.18.0-17.18 -proposed tracker (LP: #1819624)
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
* C++ demangling support missing from perf (LP: #1396654)
- [Packaging] fix a mistype
* arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout (LP: #1818162)
- iommu/arm-smmu-v3: Fix unexpected CMD_SYNC timeout
* Crash in nvme_irq_check() when using threaded interrupts (LP: #1818747)
- nvme-pci: fix out of bounds access in nvme_cqe_pending
* CVE-2019-9003
- ipmi: fix use-after-free of user->release_barrier.rda
* CVE-2019-9162
- netfilter: nf_nat_snmp_basic: add missing length checks in ASN.1 cbs
* CVE-2019-9213
- mm: enforce min addr even if capable() in expand_downwards()
* CVE-2019-3460
- Bluetooth: Check L2CAP option sizes returned from l2cap_get_conf_opt
* tun/tap: unable to manage carrier state from userland (LP: #1806392)
- tun: implement carrier change
* CVE-2019-8980
- exec: Fix mem leak in kernel_read_file
* [Packaging] Allow overlay of config annotations (LP: #1752072)
- [Packaging] config-check: Add an include directive
* amdgpu with mst WARNING on blanking (LP: #1814308)
- drm/amd/display: Fix MST dp_blank REG_WAIT timeout
* CVE-2019-7308
- bpf: move {prev_,}insn_idx into verifier env
- bpf: move tmp variable into ax register in interpreter
- bpf: enable access to ax register also from verifier rewrite
- bpf: restrict map value pointer arithmetic for unprivileged
- bpf: restrict stack pointer arithmetic for unprivileged
- bpf: restrict unknown scalars of mixed signed bounds for unprivileged
- bpf: fix check_map_access smin_value test when pointer contains offset
- bpf: prevent out of bounds speculation on pointer arithmetic
- bpf: fix sanitation of alu op with pointer / scalar type from different
paths
- bpf: add various test cases to test_verifier
- bpf: add various test cases to selftests
* CVE-2017-5753
- bpf: fix inner map masking to prevent oob under speculation
* Use memblock quirk instead of delayed allocation for GICv3 LPI tables
(LP: #1816425)
- efi/arm: Revert "Defer persistent reservations until after paging_init()"
- arm64, mm, efi: Account for GICv3 LPI tables in static memblock reserve
table
* efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted (LP: #1814982)
- efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted
* Update ENA driver to version 2.0.3K (LP: #1816806)
- net: ena: update driver version from 2.0.2 to 2.0.3
- net: ena: fix race between link up and device initalization
- net: ena: fix crash during failed resume from hibernation
* Silent "Unknown key" message when pressing keyboard backlight hotkey
(LP: #1817063)
- platform/x86: dell-wmi: Ignore new keyboard backlight change event
* CVE-2018-19824
- ALSA: usb-audio: Fix UAF decrement if card has no live interfaces in
card.c
* CVE-2019-3459
- Bluetooth: Verify that l2cap_get_conf_opt provides large enough buffer
* CONFIG_TEST_BPF is disabled (LP: #1813955)
- [Config]: Reenable TEST_BPF
* installer does not support iSCSI iBFT (LP: #1817321)
- d-i: add iscsi_ibft to scsi-modules
* CVE-2019-7222
- KVM: x86: work around leak of uninitialized stack contents (CVE-2019-7222)
* CVE-2019-7221
- KVM: nVMX: unconditionally cancel preemption timer in free_nested
(CVE-2019-7221)
* CVE-2019-6974
- kvm: fix kvm_ioctl_create_device() reference counting (CVE-2019-6974)
* hns3 nic speed may not match optical port speed (LP: #1817969)
- net: hns3: Config NIC port speed same as that of optical module
* [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() (LP: #1802021)
- srcu: Lock srcu_data structure in srcu_gp_start()
* libsas disks can have non-unique by-path names (LP: #1817784)
- scsi: libsas: Fix rphy phy_identifier for PHYs with end devices attached
* Bluetooth not working (Intel CyclonePeak) (LP: #1817518)
- Bluetooth: btusb: Add support for Intel bluetooth device 8087:0029
* CVE-2019-8912
- net: crypto set sk to NULL when af_alg_release.
- net: socket: set sock->sk to NULL after calling proto_ops::release()
* 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable (LP: #1812099)
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
This bug was fixed in the package linux-azure - 4.18.0-1014.14
---
linux-azure (4.18.0-1014.14) cosmic; urgency=medium
* linux-azure: 4.18.0-1014.14 -proposed tracker (LP: #1819618)
* PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was
expected to be set in C-KVM (LP: #1812624)
- [Config]: enable PAGE_POISONING, PAGE_POISONING_NO_SANITY,
PAGE_POISONING_ZERO
* Add CONFIG_NO_HZ_FULL=y to linux-azure kernels (LP: #1818138)
- [Config] linux-azure: CONFIG_NO_HZ_FULL=y
[ Ubuntu: 4.18.0-17.18 ]
* linux: 4.18.0-17.18 -proposed tracker (LP: #1819624)
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
* C++ demangling support missing from perf (LP: #1396654)
- [Packaging] fix a mistype
* arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout (LP: #1818162)
- iommu/arm-smmu-v3: Fix unexpected CMD_SYNC timeout
* Crash in nvme_irq_check() when using threaded interrupts (LP: #1818747)
- nvme-pci: fix out of bounds access in nvme_cqe_pending
* CVE-2019-9003
- ipmi: fix use-after-free of user->release_barrier.rda
* CVE-2019-9162
- netfilter: nf_nat_snmp_basic: add missing length checks in ASN.1 cbs
* CVE-2019-9213
- mm: enforce min addr even if capable() in expand_downwards()
* CVE-2019-3460
- Bluetooth: Check L2CAP option sizes returned from l2cap_get_conf_opt
* tun/tap: unable to manage carrier state from userland (LP: #1806392)
- tun: implement carrier change
* CVE-2019-8980
- exec: Fix mem leak in kernel_read_file
* [Packaging] Allow overlay of config annotations (LP: #1752072)
- [Packaging] config-check: Add an include directive
* amdgpu with mst WARNING on blanking (LP: #1814308)
- drm/amd/display: Fix MST dp_blank REG_WAIT timeout
* CVE-2019-7308
- bpf: move {prev_,}insn_idx into verifier env
- bpf: move tmp variable into ax register in interpreter
- bpf: enable access to ax register also from verifier rewrite
- bpf: restrict map value pointer arithmetic for unprivileged
- bpf: restrict stack pointer arithmetic for unprivileged
- bpf: restrict unknown scalars of mixed signed bounds for unprivileged
- bpf: fix check_map_access smin_value test when pointer contains offset
- bpf: prevent out of bounds speculation on pointer arithmetic
- bpf: fix sanitation of alu op with pointer / scalar type from different
paths
- bpf: add various test cases to test_verifier
- bpf: add various test cases to selftests
* CVE-2017-5753
- bpf: fix inner map masking to prevent oob under speculation
* Use memblock quirk instead of delayed allocation for GICv3 LPI tables
(LP: #1816425)
- efi/arm: Revert "Defer persistent reservations until after paging_init()"
- arm64, mm, efi: Account for GICv3 LPI tables in static memblock reserve
table
* efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted (LP: #1814982)
- efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted
* Update ENA driver to version 2.0.3K (LP: #1816806)
- net: ena: update driver version from 2.0.2 to 2.0.3
- net: ena: fix race between link up and device initalization
- net: ena: fix crash during failed resume from hibernation
* Silent "Unknown key" message when pressing keyboard backlight hotkey
(LP: #1817063)
- platform/x86: dell-wmi: Ignore new keyboard backlight change event
* CVE-2018-19824
- ALSA: usb-audio: Fix UAF decrement if card has no live interfaces in
card.c
* CVE-2019-3459
- Bluetooth: Verify that l2cap_get_conf_opt provides large enough buffer
* CONFIG_TEST_BPF is disabled (LP: #1813955)
- [Config]: Reenable TEST_BPF
* installer does not support iSCSI iBFT (LP: #1817321)
- d-i: add iscsi_ibft to scsi-modules
* CVE-2019-7222
- KVM: x86: work around leak of uninitialized stack contents (CVE-2019-7222)
* CVE-2019-7221
- KVM: nVMX: unconditionally cancel preemption timer in free_nested
(CVE-2019-7221)
* CVE-2019-6974
- kvm: fix kvm_ioctl_create_device() reference counting (CVE-2019-6974)
* hns3 nic speed may not match optical port speed (LP: #1817969)
- net: hns3: Config NIC port speed same as that of optical module
* [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() (LP: #1802021)
- srcu: Lock srcu_data structure in srcu_gp_start()
* libsas disks can have non-unique by-path names (LP: #1817784)
- scsi: libsas: Fix rphy phy_identifier for PHYs with end devices attached
* Bluetooth not working (Intel CyclonePeak) (LP: #1817518)
- Bluetooth: btusb: Add support for Intel bluetooth device 8087:0029
* CVE-2019-8912
- net: crypto set sk to NULL when af_alg_release.
- net: socket: set sock->sk to NULL after calling proto_ops::release()
* 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable (LP: #1812099)
- platform/x86: thinkpad_acpi: Fix multi-battery bug
* [ALSA] [PATCH]
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
This bug was fixed in the package linux-aws - 4.18.0-1011.13 --- linux-aws (4.18.0-1011.13) cosmic; urgency=medium * linux-aws: 4.18.0-1011.13 -proposed tracker (LP: #1814757) * PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM (LP: #1812624) - [Config]: enable PAGE_POISONING, PAGE_POISONING_NO_SANITY, PAGE_POISONING_ZERO * Update ENA driver to version 2.0.3K (LP: #1816806) - net: ena: fix crash during failed resume from hibernation - net: ena: fix race between link up and device initalization - net: ena: update driver version from 2.0.2 to 2.0.3 * xen hibernation support for linux-aws (bionic+) (LP: #1804533) - SAUCE [aws] x86/xen: Introduce new function to map HYPERVISOR_shared_info on Resume - SAUCE [aws] x86/xen: add system core suspend and resume callbacks - SAUCE [aws] xen-netfront: add callbacks for PM suspend and hibernation support - SAUCE [aws] xen-time-introduce-xen_-save-restore-_steal_clock - SAUCE [aws] x86/xen: save and restore steal clock - SAUCE [aws] xen/events: add xen_shutdown_pirqs helper function - SAUCE [aws] x86/xen: close event channels for PIRQs in system core suspend callback - SAUCE [aws] PM / hibernate: update the resume offset on SNAPSHOT_SET_SWAP_AREA * Packaging resync (LP: #1786013) - [Packaging] resync getabis - [Packaging] update helper scripts linux-aws (4.18.0-1010.12) cosmic; urgency=medium * linux-aws: 4.18.0-1010.12 -proposed tracker (LP: #1814757) * bluetooth controller not detected with 4.15 kernel (LP: #1810797) - [Config] Disable BT_QCOMSMD_HACK for AWS * Packaging resync (LP: #1786013) - [Packaging] update helper scripts [ Ubuntu: 4.18.0-16.17 ] * linux: 4.18.0-16.17 -proposed tracker (LP: #1814749) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * CVE-2018-16880 - vhost: fix OOB in get_rx_bufs() * RTL8822BE WiFi Disabled in Kernel 4.18.0-12 (LP: #1806472) - SAUCE: staging: rtlwifi: allow RTLWIFI_DEBUG_ST to be disabled - [Config] CONFIG_RTLWIFI_DEBUG_ST=n - SAUCE: Add r8822be to signature inclusion list * kernel oops in bcache module (LP: #1793901) - SAUCE: bcache: never writeback a discard operation * CVE-2018-18397 - userfaultfd: use ENOENT instead of EFAULT if the atomic copy user fails - userfaultfd: shmem: allocate anonymous memory for MAP_PRIVATE shmem - userfaultfd: shmem/hugetlbfs: only allow to register VM_MAYWRITE vmas - userfaultfd: shmem: add i_size checks - userfaultfd: shmem: UFFDIO_COPY: set the page dirty if VM_WRITE is not set * Ignore "incomplete report" from Elan touchpanels (LP: #1813733) - HID: i2c-hid: Ignore input report if there's no data present on Elan touchpanels * Vsock connect fails with ENODEV for large CID (LP: #1813934) - vhost/vsock: fix vhost vsock cid hashing inconsistent * Fix non-working pinctrl-intel (LP: #1811777) - pinctrl: intel: Do pin translation in other GPIO operations as well * ip6_gre: fix tunnel list corruption for x-netns (LP: #1812875) - ip6_gre: fix tunnel list corruption for x-netns * Backported commit breaks audio (fixed upstream) (LP: #1811566) - ASoC: intel: cht_bsw_max98090_ti: Add quirk for boards using pmc_plt_clk_0 - ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Clapper - ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Gnawty * kvm_stat : missing python dependency (LP: #1798776) - tools/kvm_stat: switch to python3 * [SRU] Fix Xorg crash with nomodeset when BIOS enable 64-bit fb addr (LP: #1812797) - vgaarb: Add support for 64-bit frame buffer address - vgaarb: Keep adding VGA device in queue * Fix non-working QCA Rome Bluetooth after S3 (LP: #1812812) - USB: Add new USB LPM helpers - USB: Consolidate LPM checks to avoid enabling LPM twice * [SRU] IO's are issued with incorrect Scatter Gather Buffer (LP: #1795453) - scsi: megaraid_sas: Use 63-bit DMA addressing * x86/mm: Found insecure W+X mapping at address (ptrval)/0xc00a (LP: #1813532) - x86/mm: Do not warn about PCI BIOS W+X mappings * CVE-2019-6133 - fork: record start_time late * Fix not working Goodix touchpad (LP: #1811929) - HID: i2c-hid: Disable runtime PM on Goodix touchpad * bluetooth controller not detected with 4.15 kernel (LP: #1810797) - SAUCE: btqcomsmd: introduce BT_QCOMSMD_HACK - [Config] arm64: snapdragon: BT_QCOMSMD_HACK=y * X1 Extreme: only one of the two SSDs is loaded (LP: #1811755) - nvme-core: rework a NQN copying operation - nvme: pad fake subsys NQN vid and ssvid with zeros - nvme: introduce NVME_QUIRK_IGNORE_DEV_SUBNQN * Crash on "ip link add foo type ipip" (LP: #1811803) - SAUCE: fan: Fix NULL pointer dereference linux-aws (4.18.0-1009.11) cosmic;
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
This bug was fixed in the package linux-aws - 4.18.0-1011.13 --- linux-aws (4.18.0-1011.13) cosmic; urgency=medium * linux-aws: 4.18.0-1011.13 -proposed tracker (LP: #1814757) * PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM (LP: #1812624) - [Config]: enable PAGE_POISONING, PAGE_POISONING_NO_SANITY, PAGE_POISONING_ZERO * Update ENA driver to version 2.0.3K (LP: #1816806) - net: ena: fix crash during failed resume from hibernation - net: ena: fix race between link up and device initalization - net: ena: update driver version from 2.0.2 to 2.0.3 * xen hibernation support for linux-aws (bionic+) (LP: #1804533) - SAUCE [aws] x86/xen: Introduce new function to map HYPERVISOR_shared_info on Resume - SAUCE [aws] x86/xen: add system core suspend and resume callbacks - SAUCE [aws] xen-netfront: add callbacks for PM suspend and hibernation support - SAUCE [aws] xen-time-introduce-xen_-save-restore-_steal_clock - SAUCE [aws] x86/xen: save and restore steal clock - SAUCE [aws] xen/events: add xen_shutdown_pirqs helper function - SAUCE [aws] x86/xen: close event channels for PIRQs in system core suspend callback - SAUCE [aws] PM / hibernate: update the resume offset on SNAPSHOT_SET_SWAP_AREA * Packaging resync (LP: #1786013) - [Packaging] resync getabis - [Packaging] update helper scripts linux-aws (4.18.0-1010.12) cosmic; urgency=medium * linux-aws: 4.18.0-1010.12 -proposed tracker (LP: #1814757) * bluetooth controller not detected with 4.15 kernel (LP: #1810797) - [Config] Disable BT_QCOMSMD_HACK for AWS * Packaging resync (LP: #1786013) - [Packaging] update helper scripts [ Ubuntu: 4.18.0-16.17 ] * linux: 4.18.0-16.17 -proposed tracker (LP: #1814749) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * CVE-2018-16880 - vhost: fix OOB in get_rx_bufs() * RTL8822BE WiFi Disabled in Kernel 4.18.0-12 (LP: #1806472) - SAUCE: staging: rtlwifi: allow RTLWIFI_DEBUG_ST to be disabled - [Config] CONFIG_RTLWIFI_DEBUG_ST=n - SAUCE: Add r8822be to signature inclusion list * kernel oops in bcache module (LP: #1793901) - SAUCE: bcache: never writeback a discard operation * CVE-2018-18397 - userfaultfd: use ENOENT instead of EFAULT if the atomic copy user fails - userfaultfd: shmem: allocate anonymous memory for MAP_PRIVATE shmem - userfaultfd: shmem/hugetlbfs: only allow to register VM_MAYWRITE vmas - userfaultfd: shmem: add i_size checks - userfaultfd: shmem: UFFDIO_COPY: set the page dirty if VM_WRITE is not set * Ignore "incomplete report" from Elan touchpanels (LP: #1813733) - HID: i2c-hid: Ignore input report if there's no data present on Elan touchpanels * Vsock connect fails with ENODEV for large CID (LP: #1813934) - vhost/vsock: fix vhost vsock cid hashing inconsistent * Fix non-working pinctrl-intel (LP: #1811777) - pinctrl: intel: Do pin translation in other GPIO operations as well * ip6_gre: fix tunnel list corruption for x-netns (LP: #1812875) - ip6_gre: fix tunnel list corruption for x-netns * Backported commit breaks audio (fixed upstream) (LP: #1811566) - ASoC: intel: cht_bsw_max98090_ti: Add quirk for boards using pmc_plt_clk_0 - ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Clapper - ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Gnawty * kvm_stat : missing python dependency (LP: #1798776) - tools/kvm_stat: switch to python3 * [SRU] Fix Xorg crash with nomodeset when BIOS enable 64-bit fb addr (LP: #1812797) - vgaarb: Add support for 64-bit frame buffer address - vgaarb: Keep adding VGA device in queue * Fix non-working QCA Rome Bluetooth after S3 (LP: #1812812) - USB: Add new USB LPM helpers - USB: Consolidate LPM checks to avoid enabling LPM twice * [SRU] IO's are issued with incorrect Scatter Gather Buffer (LP: #1795453) - scsi: megaraid_sas: Use 63-bit DMA addressing * x86/mm: Found insecure W+X mapping at address (ptrval)/0xc00a (LP: #1813532) - x86/mm: Do not warn about PCI BIOS W+X mappings * CVE-2019-6133 - fork: record start_time late * Fix not working Goodix touchpad (LP: #1811929) - HID: i2c-hid: Disable runtime PM on Goodix touchpad * bluetooth controller not detected with 4.15 kernel (LP: #1810797) - SAUCE: btqcomsmd: introduce BT_QCOMSMD_HACK - [Config] arm64: snapdragon: BT_QCOMSMD_HACK=y * X1 Extreme: only one of the two SSDs is loaded (LP: #1811755) - nvme-core: rework a NQN copying operation - nvme: pad fake subsys NQN vid and ssvid with zeros - nvme: introduce NVME_QUIRK_IGNORE_DEV_SUBNQN * Crash on "ip link add foo type ipip" (LP: #1811803) - SAUCE: fan: Fix NULL pointer dereference linux-aws (4.18.0-1009.11) cosmic;
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
** Changed in: linux-azure (Ubuntu Cosmic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
In Progress
Status in linux-aws package in Ubuntu:
In Progress
Status in linux-azure package in Ubuntu:
In Progress
Status in linux-kvm package in Ubuntu:
In Progress
Status in linux-aws source package in Cosmic:
Fix Committed
Status in linux-azure source package in Cosmic:
Fix Committed
Status in linux-kvm source package in Cosmic:
Fix Committed
Status in linux-aws source package in Disco:
In Progress
Status in linux-azure source package in Disco:
In Progress
Status in linux-kvm source package in Disco:
In Progress
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 2019
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/1812624/+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
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
** Changed in: linux-aws (Ubuntu Cosmic)
Importance: Undecided => Medium
** Changed in: linux-aws (Ubuntu Cosmic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
In Progress
Status in linux-aws package in Ubuntu:
In Progress
Status in linux-azure package in Ubuntu:
In Progress
Status in linux-kvm package in Ubuntu:
In Progress
Status in linux-aws source package in Cosmic:
Fix Committed
Status in linux-azure source package in Cosmic:
In Progress
Status in linux-kvm source package in Cosmic:
Fix Committed
Status in linux-aws source package in Disco:
In Progress
Status in linux-azure source package in Disco:
In Progress
Status in linux-kvm source package in Disco:
In Progress
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 2019
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/1812624/+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
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
** Changed in: linux-kvm (Ubuntu Cosmic)
Importance: Undecided => Medium
** Changed in: linux-kvm (Ubuntu Cosmic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
In Progress
Status in linux-aws package in Ubuntu:
In Progress
Status in linux-azure package in Ubuntu:
In Progress
Status in linux-kvm package in Ubuntu:
In Progress
Status in linux-aws source package in Cosmic:
In Progress
Status in linux-azure source package in Cosmic:
In Progress
Status in linux-kvm source package in Cosmic:
Fix Committed
Status in linux-aws source package in Disco:
In Progress
Status in linux-azure source package in Disco:
In Progress
Status in linux-kvm source package in Disco:
In Progress
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 2019
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/1812624/+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
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
It looks like azure disco is affected too, change the status
accordingly.
** Changed in: linux-azure (Ubuntu Cosmic)
Status: Confirmed => In Progress
** Changed in: linux-azure (Ubuntu Cosmic)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux-azure (Ubuntu Disco)
Status: Invalid => In Progress
** Changed in: linux-azure (Ubuntu Disco)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
In Progress
Status in linux-aws package in Ubuntu:
In Progress
Status in linux-azure package in Ubuntu:
In Progress
Status in linux-kvm package in Ubuntu:
In Progress
Status in linux-aws source package in Cosmic:
In Progress
Status in linux-azure source package in Cosmic:
In Progress
Status in linux-kvm source package in Cosmic:
In Progress
Status in linux-aws source package in Disco:
In Progress
Status in linux-azure source package in Disco:
In Progress
Status in linux-kvm source package in Disco:
In Progress
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 2019
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/1812624/+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
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
** Changed in: ubuntu-kernel-tests
Status: New => In Progress
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
In Progress
Status in linux-aws package in Ubuntu:
In Progress
Status in linux-azure package in Ubuntu:
Invalid
Status in linux-kvm package in Ubuntu:
In Progress
Status in linux-aws source package in Cosmic:
In Progress
Status in linux-azure source package in Cosmic:
Confirmed
Status in linux-kvm source package in Cosmic:
In Progress
Status in linux-aws source package in Disco:
In Progress
Status in linux-azure source package in Disco:
Invalid
Status in linux-kvm source package in Disco:
In Progress
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 2019
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/1812624/+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
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
** Changed in: linux-aws (Ubuntu Cosmic)
Status: Confirmed => In Progress
** Changed in: linux-aws (Ubuntu Cosmic)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux-aws (Ubuntu Disco)
Status: Confirmed => In Progress
** Changed in: linux-aws (Ubuntu Disco)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
New
Status in linux-aws package in Ubuntu:
In Progress
Status in linux-azure package in Ubuntu:
Invalid
Status in linux-kvm package in Ubuntu:
In Progress
Status in linux-aws source package in Cosmic:
In Progress
Status in linux-azure source package in Cosmic:
Confirmed
Status in linux-kvm source package in Cosmic:
In Progress
Status in linux-aws source package in Disco:
In Progress
Status in linux-azure source package in Disco:
Invalid
Status in linux-kvm source package in Disco:
In Progress
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 2019
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/1812624/+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
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
** Also affects: linux-aws (Ubuntu Disco)
Importance: Undecided
Status: Confirmed
** Also affects: linux-azure (Ubuntu Disco)
Importance: Undecided
Status: Invalid
** Also affects: linux-kvm (Ubuntu Disco)
Importance: Undecided
Assignee: Po-Hsu Lin (cypressyew)
Status: In Progress
** Changed in: linux-kvm (Ubuntu Cosmic)
Status: Confirmed => In Progress
** Changed in: linux-kvm (Ubuntu Cosmic)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
New
Status in linux-aws package in Ubuntu:
Confirmed
Status in linux-azure package in Ubuntu:
Invalid
Status in linux-kvm package in Ubuntu:
In Progress
Status in linux-aws source package in Cosmic:
Confirmed
Status in linux-azure source package in Cosmic:
Confirmed
Status in linux-kvm source package in Cosmic:
In Progress
Status in linux-aws source package in Disco:
Confirmed
Status in linux-azure source package in Disco:
Invalid
Status in linux-kvm source package in Disco:
In Progress
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 2019
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/1812624/+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
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
OK will do.
Thanks for the input.
** Changed in: linux-kvm (Ubuntu)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux-kvm (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
New
Status in linux-aws package in Ubuntu:
Confirmed
Status in linux-azure package in Ubuntu:
Invalid
Status in linux-kvm package in Ubuntu:
In Progress
Status in linux-aws source package in Cosmic:
Confirmed
Status in linux-azure source package in Cosmic:
Confirmed
Status in linux-kvm source package in Cosmic:
Confirmed
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 2019
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/1812624/+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
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu Cosmic)
Status: New => Confirmed
** Changed in: linux-azure (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
New
Status in linux-aws package in Ubuntu:
Confirmed
Status in linux-azure package in Ubuntu:
Invalid
Status in linux-kvm package in Ubuntu:
Confirmed
Status in linux-aws source package in Cosmic:
Confirmed
Status in linux-azure source package in Cosmic:
Confirmed
Status in linux-kvm source package in Cosmic:
Confirmed
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 2019
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/1812624/+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
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
I'm not aware of any reason that the PAGE_POISONING configs should
differ from master for any derivative kernels. Po-Hsu, if you want to
submit config patches for those affected, that would be great.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
New
Status in linux-aws package in Ubuntu:
Confirmed
Status in linux-kvm package in Ubuntu:
Confirmed
Status in linux-aws source package in Cosmic:
Confirmed
Status in linux-kvm source package in Cosmic:
Confirmed
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 2019
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/1812624/+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
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-aws (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
New
Status in linux-aws package in Ubuntu:
Confirmed
Status in linux-kvm package in Ubuntu:
Confirmed
Status in linux-aws source package in Cosmic:
Confirmed
Status in linux-kvm source package in Cosmic:
Confirmed
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 2019
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/1812624/+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
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-aws (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
New
Status in linux-aws package in Ubuntu:
Confirmed
Status in linux-kvm package in Ubuntu:
Confirmed
Status in linux-aws source package in Cosmic:
Confirmed
Status in linux-kvm source package in Cosmic:
Confirmed
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 2019
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/1812624/+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
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
** Also affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
New
Status in linux-aws package in Ubuntu:
Confirmed
Status in linux-kvm package in Ubuntu:
Confirmed
Status in linux-aws source package in Cosmic:
Confirmed
Status in linux-kvm source package in Cosmic:
Confirmed
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 2019
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/1812624/+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
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-kvm (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
New
Status in linux-aws package in Ubuntu:
Confirmed
Status in linux-kvm package in Ubuntu:
Confirmed
Status in linux-aws source package in Cosmic:
Confirmed
Status in linux-kvm source package in Cosmic:
Confirmed
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 2019
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/1812624/+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
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-kvm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
New
Status in linux-aws package in Ubuntu:
Confirmed
Status in linux-kvm package in Ubuntu:
Confirmed
Status in linux-aws source package in Cosmic:
Confirmed
Status in linux-kvm source package in Cosmic:
Confirmed
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 2019
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/1812624/+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
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
This also affects cosmic/linux-aws:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/amd64/l/linux-aws/20190115_155144_26f2e@/log.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
New
Status in linux-aws package in Ubuntu:
Confirmed
Status in linux-kvm package in Ubuntu:
Confirmed
Status in linux-aws source package in Cosmic:
Confirmed
Status in linux-kvm source package in Cosmic:
Confirmed
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 2019
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/1812624/+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
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
** Also affects: linux-kvm (Ubuntu Cosmic)
Importance: Undecided
Status: New
--
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/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
New
Status in linux-kvm package in Ubuntu:
New
Status in linux-kvm source package in Cosmic:
New
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 2019
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/1812624/+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
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
--
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/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
New
Status in linux-kvm package in Ubuntu:
New
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 2019
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/1812624/+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
