[Kernel-packages] [Bug 1769696] Re: [SRU][Bionic/Artful] fix false positives in W+X checking
This bug was fixed in the package linux - 4.15.0-23.25
---
linux (4.15.0-23.25) bionic; urgency=medium
* linux: 4.15.0-23.25 -proposed tracker (LP: #1772927)
* arm64 SDEI support needs trampoline code for KPTI (LP: #1768630)
- arm64: mmu: add the entry trampolines start/end section markers into
sections.h
- arm64: sdei: Add trampoline code for remapping the kernel
* Some PCIe errors not surfaced through rasdaemon (LP: #1769730)
- ACPI: APEI: handle PCIe AER errors in separate function
- ACPI: APEI: call into AER handling regardless of severity
* qla2xxx: Fix page fault at kmem_cache_alloc_node() (LP: #1770003)
- scsi: qla2xxx: Fix session cleanup for N2N
- scsi: qla2xxx: Remove unused argument from
qlt_schedule_sess_for_deletion()
- scsi: qla2xxx: Serialize session deletion by using work_lock
- scsi: qla2xxx: Serialize session free in qlt_free_session_done
- scsi: qla2xxx: Don't call dma_free_coherent with IRQ disabled.
- scsi: qla2xxx: Fix warning in qla2x00_async_iocb_timeout()
- scsi: qla2xxx: Prevent relogin trigger from sending too many commands
- scsi: qla2xxx: Fix double free bug after firmware timeout
- scsi: qla2xxx: Fixup locking for session deletion
* Several hisi_sas bug fixes (LP: #1768974)
- scsi: hisi_sas: dt-bindings: add an property of signal attenuation
- scsi: hisi_sas: support the property of signal attenuation for v2 hw
- scsi: hisi_sas: fix the issue of link rate inconsistency
- scsi: hisi_sas: fix the issue of setting linkrate register
- scsi: hisi_sas: increase timer expire of internal abort task
- scsi: hisi_sas: remove unused variable hisi_sas_devices.running_req
- scsi: hisi_sas: fix return value of hisi_sas_task_prep()
- scsi: hisi_sas: Code cleanup and minor bug fixes
* [bionic] machine stuck and bonding not working well when nvmet_rdma module
is loaded (LP: #1764982)
- nvmet-rdma: Don't flush system_wq by default during remove_one
- nvme-rdma: Don't flush delete_wq by default during remove_one
* Warnings/hang during error handling of SATA disks on SAS controller
(LP: #1768971)
- scsi: libsas: defer ata device eh commands to libata
* Hotplugging a SATA disk into a SAS controller may cause crash (LP: #1768948)
- ata: do not schedule hot plug if it is a sas host
* ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow by CPU
ATTEMPT TO RE-ENTER FIRMWARE! (LP: #1767927)
- powerpc/powernv: Handle unknown OPAL errors in opal_nvram_write()
- powerpc/64s: return more carefully from sreset NMI
- powerpc/64s: sreset panic if there is no debugger or crash dump handlers
* fsnotify: Fix fsnotify_mark_connector race (LP: #1765564)
- fsnotify: Fix fsnotify_mark_connector race
* Hang on network interface removal in Xen virtual machine (LP: #1771620)
- xen-netfront: Fix hang on device removal
* HiSilicon HNS NIC names are truncated in /proc/interrupts (LP: #1765977)
- net: hns: Avoid action name truncation
* Ubuntu 18.04 kernel crashed while in degraded mode (LP: #1770849)
- SAUCE: powerpc/perf: Fix memory allocation for core-imc based on
num_possible_cpus()
* Switch Build-Depends: transfig to fig2dev (LP: #1770770)
- [Config] update Build-Depends: transfig to fig2dev
* smp_call_function_single/many core hangs with stop4 alone (LP: #1768898)
- cpufreq: powernv: Fix hardlockup due to synchronous smp_call in timer
interrupt
* Add d-i support for Huawei NICs (LP: #1767490)
- d-i: add hinic to nic-modules udeb
* unregister_netdevice: waiting for eth0 to become free. Usage count = 5
(LP: #1746474)
- xfrm: reuse uncached_list to track xdsts
* Include nfp driver in linux-modules (LP: #1768526)
- [Config] Add nfp.ko to generic inclusion list
* Kernel panic on boot (m1.small in cn-north-1) (LP: #1771679)
- x86/xen: Reset VCPU0 info pointer after shared_info remap
* CVE-2018-3639 (x86)
- x86/bugs: Fix the parameters alignment and missing void
- KVM: SVM: Move spec control call after restore of GS
- x86/speculation: Use synthetic bits for IBRS/IBPB/STIBP
- x86/cpufeatures: Disentangle MSR_SPEC_CTRL enumeration from IBRS
- x86/cpufeatures: Disentangle SSBD enumeration
- x86/cpufeatures: Add FEATURE_ZEN
- x86/speculation: Handle HT correctly on AMD
- x86/bugs, KVM: Extend speculation control for VIRT_SPEC_CTRL
- x86/speculation: Add virtualized speculative store bypass disable support
- x86/speculation: Rework speculative_store_bypass_update()
- x86/bugs: Unify x86_spec_ctrl_{set_guest,restore_host}
- x86/bugs: Expose x86_spec_ctrl_base directly
- x86/bugs: Remove x86_spec_ctrl_set()
- x86/bugs: Rework spec_ctrl base and mask logic
- x86/speculation, KVM: Implement support for VIRT_SPEC_CTRL/LS_CFG
- KVM: SVM: Implement VIRT_SPEC_CTRL support for SSBD
- x86/bugs:
[Kernel-packages] [Bug 1769696] Re: [SRU][Bionic/Artful] fix false positives in W+X checking
This bug was fixed in the package linux - 4.13.0-45.50
---
linux (4.13.0-45.50) artful; urgency=medium
* linux: 4.13.0-45.50 -proposed tracker (LP: #1774124)
* CVE-2018-3639 (x86)
- SAUCE: Set generic SSBD feature for Intel cpus
linux (4.13.0-44.49) artful; urgency=medium
* linux: 4.13.0-44.49 -proposed tracker (LP: #1772951)
* CVE-2018-3639 (x86)
- x86/cpu: Make alternative_msr_write work for 32-bit code
- x86/cpu/AMD: Fix erratum 1076 (CPB bit)
- x86/bugs: Fix the parameters alignment and missing void
- KVM: SVM: Move spec control call after restore of GS
- x86/speculation: Use synthetic bits for IBRS/IBPB/STIBP
- x86/cpufeatures: Disentangle MSR_SPEC_CTRL enumeration from IBRS
- x86/cpufeatures: Disentangle SSBD enumeration
- x86/cpufeatures: Add FEATURE_ZEN
- x86/speculation: Handle HT correctly on AMD
- x86/bugs, KVM: Extend speculation control for VIRT_SPEC_CTRL
- x86/speculation: Add virtualized speculative store bypass disable support
- x86/speculation: Rework speculative_store_bypass_update()
- x86/bugs: Unify x86_spec_ctrl_{set_guest,restore_host}
- x86/bugs: Expose x86_spec_ctrl_base directly
- x86/bugs: Remove x86_spec_ctrl_set()
- x86/bugs: Rework spec_ctrl base and mask logic
- x86/speculation, KVM: Implement support for VIRT_SPEC_CTRL/LS_CFG
- KVM: SVM: Implement VIRT_SPEC_CTRL support for SSBD
- x86/bugs: Rename SSBD_NO to SSB_NO
- KVM: VMX: Expose SSBD properly to guests.
* [Ubuntu 16.04] kernel: fix rwlock implementation (LP: #1761674)
- SAUCE: (no-up) s390: fix rwlock implementation
* CVE-2018-7492
- rds: Fix NULL pointer dereference in __rds_rdma_map
* CVE-2018-8781
- drm: udl: Properly check framebuffer mmap offsets
* fsnotify: Fix fsnotify_mark_connector race (LP: #1765564)
- fsnotify: Fix fsnotify_mark_connector race
* Kernel panic on boot (m1.small in cn-north-1) (LP: #1771679)
- x86/xen: Reset VCPU0 info pointer after shared_info remap
* Suspend to idle: Open lid didn't resume (LP: #1771542)
- ACPI / PM: Do not reconfigure GPEs for suspend-to-idle
* CVE-2018-1092
- ext4: fail ext4_iget for root directory if unallocated
* [SRU][Artful] using vfio-pci on a combination of cn8xxx and some PCI devices
results in a kernel panic. (LP: #1770254)
- PCI: Avoid bus reset if bridge itself is broken
- PCI: Mark Cavium CN8xxx to avoid bus reset
- PCI: Avoid slot reset if bridge itself is broken
* Battery drains when laptop is off (shutdown) (LP: #1745646)
- PCI / PM: Check device_may_wakeup() in pci_enable_wake()
* perf record crash: refcount_inc assertion failed (LP: #1769027)
- perf cgroup: Fix refcount usage
- perf xyarray: Fix wrong processing when closing evsel fd
* Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot
(LP: #1764194)
- drm/i915/bios: filter out invalid DDC pins from VBT child devices
* Fix an issue that some PCI devices get incorrectly suspended (LP: #1764684)
- PCI / PM: Always check PME wakeup capability for runtime wakeup support
* [SRU][Bionic/Artful] fix false positives in W+X checking (LP: #1769696)
- init: fix false positives in W+X checking
* CVE-2018-1068
- netfilter: ebtables: CONFIG_COMPAT: don't trust userland offsets
* CVE-2018-8087
- mac80211_hwsim: fix possible memory leak in hwsim_new_radio_nl()
* Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in
DELL XPS 13 9370 with firmware 1.50 (LP: #1763748)
- SAUCE: media: uvcvideo: Support realtek's UVC 1.5 device
* unregister_netdevice: waiting for eth0 to become free. Usage count = 5
(LP: #1746474)
- ipv4: convert dst_metrics.refcnt from atomic_t to refcount_t
- xfrm: reuse uncached_list to track xdsts
* Acer Swift sf314-52 power button not managed (LP: #1766054)
- SAUCE: platform/x86: acer-wmi: add another KEY_POWER keycode
* set PINCFG_HEADSET_MIC to parse_flags for Dell precision 3630 (LP: #1766398)
- ALSA: hda/realtek - set PINCFG_HEADSET_MIC to parse_flags
* Change the location for one of two front mics on a lenovo thinkcentre
machine (LP: #1766477)
- ALSA: hda/realtek - adjust the location of one mic
-- Stefan Bader Mon, 28 May 2018 16:10:36
+0200
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1769696
Title:
[SRU][Bionic/Artful] fix false positives in W+X checking
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Artful:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
[Impact]
on ARM64 servers we observe call trace "arm64/mm: Found insecure W+X mapping
at address 00a99000/0xa99000" while booting. These messages are a false
[Kernel-packages] [Bug 1769696] Re: [SRU][Bionic/Artful] fix false positives in W+X checking
This bug was fixed in the package linux - 4.4.0-128.154
---
linux (4.4.0-128.154) xenial; urgency=medium
* linux: 4.4.0-128.154 -proposed tracker (LP: #1772960)
* CVE-2018-3639 (x86)
- x86/cpu: Make alternative_msr_write work for 32-bit code
- x86/bugs: Fix the parameters alignment and missing void
- KVM: SVM: Move spec control call after restore of GS
- x86/speculation: Use synthetic bits for IBRS/IBPB/STIBP
- x86/cpufeatures: Disentangle MSR_SPEC_CTRL enumeration from IBRS
- x86/cpufeatures: Disentangle SSBD enumeration
- x86/cpu/AMD: Fix erratum 1076 (CPB bit)
- x86/cpufeatures: Add FEATURE_ZEN
- x86/speculation: Handle HT correctly on AMD
- x86/bugs, KVM: Extend speculation control for VIRT_SPEC_CTRL
- x86/speculation: Add virtualized speculative store bypass disable support
- x86/speculation: Rework speculative_store_bypass_update()
- x86/bugs: Unify x86_spec_ctrl_{set_guest,restore_host}
- x86/bugs: Expose x86_spec_ctrl_base directly
- x86/bugs: Remove x86_spec_ctrl_set()
- x86/bugs: Rework spec_ctrl base and mask logic
- x86/speculation, KVM: Implement support for VIRT_SPEC_CTRL/LS_CFG
- KVM: SVM: Implement VIRT_SPEC_CTRL support for SSBD
- x86/bugs: Rename SSBD_NO to SSB_NO
- KVM: VMX: Expose SSBD properly to guests.
* [i915_bpo] Fix flickering issue after panel change (LP: #1770565)
- drm/i915: Fix iboost setting for DDI with 4 lanes on SKL
- drm/i915: Name the "iboost bit"
- drm/i915: Program iboost settings for HDMI/DVI on SKL
- drm/i915: Move bxt_ddi_vswing_sequence() call into intel_ddi_pre_enable()
for HDMI
- drm/i915: Explicitly use ddi buf trans entry 9 for hdmi
- drm/i915: Split DP/eDP/FDI and HDMI/DVI DDI buffer programming apart
- drm/i915: Get the iboost setting based on the port type
- drm/i915: Simplify intel_ddi_get_encoder_port()
- drm/i915: Fix iboost setting for SKL Y/U DP DDI buffer translation entry 2
- drm/i915: KBL - Recommended buffer translation programming for DisplayPort
- drm/i915: Ignore OpRegion panel type except on select machines
* [SRU][Bionic/Artful] fix false positives in W+X checking (LP: #1769696)
- init: fix false positives in W+X checking
* [Ubuntu 16.04] kernel: fix rwlock implementation (LP: #1761674)
- SAUCE: (no-up) s390: fix rwlock implementation
* linux < 4.11: unable to use netfilter logging from non-init namespaces
(LP: #1766573)
- netfilter: allow logging from non-init namespaces
* [LTC Test] Ubuntu 18.04: tm_sigreturn failed on P8 compat mode 16.04.04
guest (LP: #1771439)
- powerpc: signals: Discard transaction state from signal frames
* QCA9377 requires more IRAM banks for its new firmware (LP: #1748345)
- ath10k: update the IRAM bank number for QCA9377
* i915/kbl_dmc_ver1.bin failed with error -2 package 1.157.17 kernel
4.4.0-116-generic (LP: #1752536)
- ubuntu: i915_bpo - Add MODULE_FIRMWARE for Geminilake's DMC
* Xenial update to 4.4.131 stable release (LP: #1768825)
- ext4: prevent right-shifting extents beyond EXT_MAX_BLOCKS
- ext4: set h_journal if there is a failure starting a reserved handle
- ext4: add validity checks for bitmap block numbers
- ext4: fix bitmap position validation
- usbip: usbip_host: fix to hold parent lock for device_attach() calls
- usbip: vhci_hcd: Fix usb device and sockfd leaks
- USB: serial: simple: add libtransistor console
- USB: serial: ftdi_sio: use jtag quirk for Arrow USB Blaster
- USB: serial: cp210x: add ID for NI USB serial console
- usb: core: Add quirk for HP v222w 16GB Mini
- USB: Increment wakeup count on remote wakeup.
- ALSA: usb-audio: Skip broken EU on Dell dock USB-audio
- virtio: add ability to iterate over vqs
- virtio_console: free buffers after reset
- drm/virtio: fix vq wait_event condition
- tty: Don't call panic() at tty_ldisc_init()
- tty: n_gsm: Fix long delays with control frame timeouts in ADM mode
- tty: n_gsm: Fix DLCI handling for ADM mode if debug & 2 is not set
- tty: Use __GFP_NOFAIL for tty_ldisc_get()
- ALSA: core: Report audio_tstamp in snd_pcm_sync_ptr
- ALSA: seq: oss: Fix unbalanced use lock for synth MIDI device
- ALSA: hda/realtek - Add some fixes for ALC233
- mtd: cfi: cmdset_0001: Do not allow read/write to suspend erase block.
- mtd: cfi: cmdset_0001: Workaround Micron Erase suspend bug.
- mtd: cfi: cmdset_0002: Do not allow read/write to suspend erase block.
- kobject: don't use WARN for registration failures
- scsi: sd: Defer spinning up drive while SANITIZE is in progress
- ARM: amba: Make driver_override output consistent with other buses
- ARM: amba: Fix race condition with driver_override
- ARM: amba: Don't read past the end of sysfs "driver_override" buffer
- ASoC: fsl_esai: Fix divisor calculation failure at lower ratio
- libceph:
[Kernel-packages] [Bug 1769696] Re: [SRU][Bionic/Artful] fix false positives in W+X checking
This bug was fixed in the package linux - 4.15.0-23.25
---
linux (4.15.0-23.25) bionic; urgency=medium
* linux: 4.15.0-23.25 -proposed tracker (LP: #1772927)
* arm64 SDEI support needs trampoline code for KPTI (LP: #1768630)
- arm64: mmu: add the entry trampolines start/end section markers into
sections.h
- arm64: sdei: Add trampoline code for remapping the kernel
* Some PCIe errors not surfaced through rasdaemon (LP: #1769730)
- ACPI: APEI: handle PCIe AER errors in separate function
- ACPI: APEI: call into AER handling regardless of severity
* qla2xxx: Fix page fault at kmem_cache_alloc_node() (LP: #1770003)
- scsi: qla2xxx: Fix session cleanup for N2N
- scsi: qla2xxx: Remove unused argument from
qlt_schedule_sess_for_deletion()
- scsi: qla2xxx: Serialize session deletion by using work_lock
- scsi: qla2xxx: Serialize session free in qlt_free_session_done
- scsi: qla2xxx: Don't call dma_free_coherent with IRQ disabled.
- scsi: qla2xxx: Fix warning in qla2x00_async_iocb_timeout()
- scsi: qla2xxx: Prevent relogin trigger from sending too many commands
- scsi: qla2xxx: Fix double free bug after firmware timeout
- scsi: qla2xxx: Fixup locking for session deletion
* Several hisi_sas bug fixes (LP: #1768974)
- scsi: hisi_sas: dt-bindings: add an property of signal attenuation
- scsi: hisi_sas: support the property of signal attenuation for v2 hw
- scsi: hisi_sas: fix the issue of link rate inconsistency
- scsi: hisi_sas: fix the issue of setting linkrate register
- scsi: hisi_sas: increase timer expire of internal abort task
- scsi: hisi_sas: remove unused variable hisi_sas_devices.running_req
- scsi: hisi_sas: fix return value of hisi_sas_task_prep()
- scsi: hisi_sas: Code cleanup and minor bug fixes
* [bionic] machine stuck and bonding not working well when nvmet_rdma module
is loaded (LP: #1764982)
- nvmet-rdma: Don't flush system_wq by default during remove_one
- nvme-rdma: Don't flush delete_wq by default during remove_one
* Warnings/hang during error handling of SATA disks on SAS controller
(LP: #1768971)
- scsi: libsas: defer ata device eh commands to libata
* Hotplugging a SATA disk into a SAS controller may cause crash (LP: #1768948)
- ata: do not schedule hot plug if it is a sas host
* ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow by CPU
ATTEMPT TO RE-ENTER FIRMWARE! (LP: #1767927)
- powerpc/powernv: Handle unknown OPAL errors in opal_nvram_write()
- powerpc/64s: return more carefully from sreset NMI
- powerpc/64s: sreset panic if there is no debugger or crash dump handlers
* fsnotify: Fix fsnotify_mark_connector race (LP: #1765564)
- fsnotify: Fix fsnotify_mark_connector race
* Hang on network interface removal in Xen virtual machine (LP: #1771620)
- xen-netfront: Fix hang on device removal
* HiSilicon HNS NIC names are truncated in /proc/interrupts (LP: #1765977)
- net: hns: Avoid action name truncation
* Ubuntu 18.04 kernel crashed while in degraded mode (LP: #1770849)
- SAUCE: powerpc/perf: Fix memory allocation for core-imc based on
num_possible_cpus()
* Switch Build-Depends: transfig to fig2dev (LP: #1770770)
- [Config] update Build-Depends: transfig to fig2dev
* smp_call_function_single/many core hangs with stop4 alone (LP: #1768898)
- cpufreq: powernv: Fix hardlockup due to synchronous smp_call in timer
interrupt
* Add d-i support for Huawei NICs (LP: #1767490)
- d-i: add hinic to nic-modules udeb
* unregister_netdevice: waiting for eth0 to become free. Usage count = 5
(LP: #1746474)
- xfrm: reuse uncached_list to track xdsts
* Include nfp driver in linux-modules (LP: #1768526)
- [Config] Add nfp.ko to generic inclusion list
* Kernel panic on boot (m1.small in cn-north-1) (LP: #1771679)
- x86/xen: Reset VCPU0 info pointer after shared_info remap
* CVE-2018-3639 (x86)
- x86/bugs: Fix the parameters alignment and missing void
- KVM: SVM: Move spec control call after restore of GS
- x86/speculation: Use synthetic bits for IBRS/IBPB/STIBP
- x86/cpufeatures: Disentangle MSR_SPEC_CTRL enumeration from IBRS
- x86/cpufeatures: Disentangle SSBD enumeration
- x86/cpufeatures: Add FEATURE_ZEN
- x86/speculation: Handle HT correctly on AMD
- x86/bugs, KVM: Extend speculation control for VIRT_SPEC_CTRL
- x86/speculation: Add virtualized speculative store bypass disable support
- x86/speculation: Rework speculative_store_bypass_update()
- x86/bugs: Unify x86_spec_ctrl_{set_guest,restore_host}
- x86/bugs: Expose x86_spec_ctrl_base directly
- x86/bugs: Remove x86_spec_ctrl_set()
- x86/bugs: Rework spec_ctrl base and mask logic
- x86/speculation, KVM: Implement support for VIRT_SPEC_CTRL/LS_CFG
- KVM: SVM: Implement VIRT_SPEC_CTRL support for SSBD
- x86/bugs:
[Kernel-packages] [Bug 1769696] Re: [SRU][Bionic/Artful] fix false positives in W+X checking
-- Bionic verification -- ubuntu@starbuck:~$ uname -a Linux starbuck 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:52 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@starbuck:~$ dmesg | grep -i "W+X" [ 34.983869] Checked W+X mappings: passed, no W+X pages found ubuntu@starbuck:~$ -- Artful verification -- ubuntu@starbuck:~$ uname -a Linux starbuck 4.13.0-45-generic #50-Ubuntu SMP Wed May 30 08:23:03 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@starbuck:~$dmesg | grep -i "W+X" [ 35.566350] Checked W+X mappings: passed, no W+X pages found ubuntu@starbuck:~$ -- Xenial Verification -- ubuntu@seuss:~$ uname -a Linux seuss 4.4.0-128-generic #154-Ubuntu SMP Fri May 25 14:17:06 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@seuss:~$ dmesg | grep -i "W+X" ubuntu@seuss:~$ ** Tags removed: verification-needed-artful verification-needed-bionic verification-needed-xenial ** Tags added: verification-done-artful verification-done-bionic verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769696 Title: [SRU][Bionic/Artful] fix false positives in W+X checking Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] on ARM64 servers we observe call trace "arm64/mm: Found insecure W+X mapping at address 00a99000/0xa99000" while booting. These messages are a false positive and triggered at random. [Test] There is no reliable way to reproduce these warnings, they are triggered at random. But these messages can appear on any ARM64 server Cavium, Qualcomm etc. A test kernel is available in ppa:manjo/lp1769696 and the kernel was boot tested on a QDF2400 system and Cavium Thunderx. ubuntu@awrep2:~$ uname -a Linux awrep2 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ uname -a Linux boomer 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ [Fix] Upstream fix is available in linux-next 65d313ee1a7d init: fix false positives in W+X checking [Regression Potential] potential for any regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769696/+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 1769696] Re: [SRU][Bionic/Artful] fix false positives in W+X checking
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769696 Title: [SRU][Bionic/Artful] fix false positives in W+X checking Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] on ARM64 servers we observe call trace "arm64/mm: Found insecure W+X mapping at address 00a99000/0xa99000" while booting. These messages are a false positive and triggered at random. [Test] There is no reliable way to reproduce these warnings, they are triggered at random. But these messages can appear on any ARM64 server Cavium, Qualcomm etc. A test kernel is available in ppa:manjo/lp1769696 and the kernel was boot tested on a QDF2400 system and Cavium Thunderx. ubuntu@awrep2:~$ uname -a Linux awrep2 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ uname -a Linux boomer 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ [Fix] Upstream fix is available in linux-next 65d313ee1a7d init: fix false positives in W+X checking [Regression Potential] potential for any regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769696/+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 1769696] Re: [SRU][Bionic/Artful] fix false positives in W+X checking
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed- artful'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769696 Title: [SRU][Bionic/Artful] fix false positives in W+X checking Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] on ARM64 servers we observe call trace "arm64/mm: Found insecure W+X mapping at address 00a99000/0xa99000" while booting. These messages are a false positive and triggered at random. [Test] There is no reliable way to reproduce these warnings, they are triggered at random. But these messages can appear on any ARM64 server Cavium, Qualcomm etc. A test kernel is available in ppa:manjo/lp1769696 and the kernel was boot tested on a QDF2400 system and Cavium Thunderx. ubuntu@awrep2:~$ uname -a Linux awrep2 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ uname -a Linux boomer 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ [Fix] Upstream fix is available in linux-next 65d313ee1a7d init: fix false positives in W+X checking [Regression Potential] potential for any regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769696/+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 1769696] Re: [SRU][Bionic/Artful] fix false positives in W+X checking
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769696 Title: [SRU][Bionic/Artful] fix false positives in W+X checking Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] on ARM64 servers we observe call trace "arm64/mm: Found insecure W+X mapping at address 00a99000/0xa99000" while booting. These messages are a false positive and triggered at random. [Test] There is no reliable way to reproduce these warnings, they are triggered at random. But these messages can appear on any ARM64 server Cavium, Qualcomm etc. A test kernel is available in ppa:manjo/lp1769696 and the kernel was boot tested on a QDF2400 system and Cavium Thunderx. ubuntu@awrep2:~$ uname -a Linux awrep2 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ uname -a Linux boomer 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ [Fix] Upstream fix is available in linux-next 65d313ee1a7d init: fix false positives in W+X checking [Regression Potential] potential for any regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769696/+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 1769696] Re: [SRU][Bionic/Artful] fix false positives in W+X checking
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769696 Title: [SRU][Bionic/Artful] fix false positives in W+X checking Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] on ARM64 servers we observe call trace "arm64/mm: Found insecure W+X mapping at address 00a99000/0xa99000" while booting. These messages are a false positive and triggered at random. [Test] There is no reliable way to reproduce these warnings, they are triggered at random. But these messages can appear on any ARM64 server Cavium, Qualcomm etc. A test kernel is available in ppa:manjo/lp1769696 and the kernel was boot tested on a QDF2400 system and Cavium Thunderx. ubuntu@awrep2:~$ uname -a Linux awrep2 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ uname -a Linux boomer 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ [Fix] Upstream fix is available in linux-next 65d313ee1a7d init: fix false positives in W+X checking [Regression Potential] potential for any regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769696/+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 1769696] Re: [SRU][Bionic/Artful] fix false positives in W+X checking
** Changed in: linux (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769696 Title: [SRU][Bionic/Artful] fix false positives in W+X checking Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: In Progress Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] on ARM64 servers we observe call trace "arm64/mm: Found insecure W+X mapping at address 00a99000/0xa99000" while booting. These messages are a false positive and triggered at random. [Test] There is no reliable way to reproduce these warnings, they are triggered at random. But these messages can appear on any ARM64 server Cavium, Qualcomm etc. A test kernel is available in ppa:manjo/lp1769696 and the kernel was boot tested on a QDF2400 system and Cavium Thunderx. ubuntu@awrep2:~$ uname -a Linux awrep2 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ uname -a Linux boomer 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ [Fix] Upstream fix is available in linux-next 65d313ee1a7d init: fix false positives in W+X checking [Regression Potential] potential for any regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769696/+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 1769696] Re: [SRU][Bionic/Artful] fix false positives in W+X checking
** Changed in: linux (Ubuntu Artful) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Artful) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769696 Title: [SRU][Bionic/Artful] fix false positives in W+X checking Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] on ARM64 servers we observe call trace "arm64/mm: Found insecure W+X mapping at address 00a99000/0xa99000" while booting. These messages are a false positive and triggered at random. [Test] There is no reliable way to reproduce these warnings, they are triggered at random. But these messages can appear on any ARM64 server Cavium, Qualcomm etc. A test kernel is available in ppa:manjo/lp1769696 and the kernel was boot tested on a QDF2400 system and Cavium Thunderx. ubuntu@awrep2:~$ uname -a Linux awrep2 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ uname -a Linux boomer 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ [Fix] Upstream fix is available in linux-next 65d313ee1a7d init: fix false positives in W+X checking [Regression Potential] potential for any regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769696/+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 1769696] Re: [SRU][Bionic/Artful] fix false positives in W+X checking
** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Artful) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769696 Title: [SRU][Bionic/Artful] fix false positives in W+X checking Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux source package in Artful: New Status in linux source package in Bionic: New Bug description: [Impact] on ARM64 servers we observe call trace "arm64/mm: Found insecure W+X mapping at address 00a99000/0xa99000" while booting. These messages are a false positive and triggered at random. [Test] There is no reliable way to reproduce these warnings, they are triggered at random. But these messages can appear on any ARM64 server Cavium, Qualcomm etc. A test kernel is available in ppa:manjo/lp1769696 and the kernel was boot tested on a QDF2400 system and Cavium Thunderx. ubuntu@awrep2:~$ uname -a Linux awrep2 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ uname -a Linux boomer 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ [Fix] Upstream fix is available in linux-next 65d313ee1a7d init: fix false positives in W+X checking [Regression Potential] potential for any regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769696/+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 1769696] Re: [SRU][Bionic/Artful] fix false positives in W+X checking
** Description changed: [Impact] on ARM64 servers we observe call trace "arm64/mm: Found insecure W+X mapping at address 00a99000/0xa99000" while booting. These messages are a false positive and triggered at random. [Test] - There is no reliable way to reproduce these warnings, they are triggered at random. But these messages can appear on any ARM64 server Cavium, Qualcomm etc. A test kernel is available in - ppa:manjo/lp1769696 and the kernel was boot tested on a QDF2400 system. + There is no reliable way to reproduce these warnings, they are triggered at random. But these messages can appear on any ARM64 server Cavium, Qualcomm etc. A test kernel is available in + ppa:manjo/lp1769696 and the kernel was boot tested on a QDF2400 system and Cavium Thunderx. - ubuntu@awrep2:~$ uname -a + ubuntu@awrep2:~$ uname -a Linux awrep2 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux + + ubuntu@boomer:~$ uname -a + Linux boomer 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux + ubuntu@boomer:~$ + [Fix] Upstream fix is available in linux-next 65d313ee1a7d init: fix false positives in W+X checking [Regression Potential] potential for any regression is low. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769696 Title: [SRU][Bionic/Artful] fix false positives in W+X checking Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux source package in Artful: New Status in linux source package in Bionic: New Bug description: [Impact] on ARM64 servers we observe call trace "arm64/mm: Found insecure W+X mapping at address 00a99000/0xa99000" while booting. These messages are a false positive and triggered at random. [Test] There is no reliable way to reproduce these warnings, they are triggered at random. But these messages can appear on any ARM64 server Cavium, Qualcomm etc. A test kernel is available in ppa:manjo/lp1769696 and the kernel was boot tested on a QDF2400 system and Cavium Thunderx. ubuntu@awrep2:~$ uname -a Linux awrep2 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ uname -a Linux boomer 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ [Fix] Upstream fix is available in linux-next 65d313ee1a7d init: fix false positives in W+X checking [Regression Potential] potential for any regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769696/+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
