[Bug 2080563] Re: Backport "x86/kaslr: Expose and use the end of the physical memory address space"
** Tags added: kernel-daily-bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080563 Title: Backport "x86/kaslr: Expose and use the end of the physical memory address space" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2080563/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080563] Re: Backport "x86/kaslr: Expose and use the end of the physical memory address space"
This bug is awaiting verification that the linux-gcp-tcpx/6.8.0-1002.3 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-jammy-linux-gcp-tcpx' to 'verification-done- jammy-linux-gcp-tcpx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-gcp-tcpx' to 'verification-failed- jammy-linux-gcp-tcpx'. 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: kernel-spammed-jammy-linux-gcp-tcpx-v2 verification-needed-jammy-linux-gcp-tcpx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080563 Title: Backport "x86/kaslr: Expose and use the end of the physical memory address space" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2080563/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080563] Re: Backport "x86/kaslr: Expose and use the end of the physical memory address space"
This bug is awaiting verification that the linux- gcp-5.4/5.4.0-1140.149~18.04.1 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-linux- gcp-5.4' to 'verification-done-bionic-linux-gcp-5.4'. If the problem still exists, change the tag 'verification-needed-bionic-linux-gcp-5.4' to 'verification-failed-bionic-linux-gcp-5.4'. 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: kernel-spammed-bionic-linux-gcp-5.4-v2 verification-needed-bionic-linux-gcp-5.4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080563 Title: Backport "x86/kaslr: Expose and use the end of the physical memory address space" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2080563/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080563] Re: Backport "x86/kaslr: Expose and use the end of the physical memory address space"
This bug was fixed in the package linux-gcp - 5.15.0-1071.79 --- linux-gcp (5.15.0-1071.79) jammy; urgency=medium * jammy/linux-gcp: 5.15.0-1071.79 -proposed tracker (LP: #2082966) * Backport "x86/kaslr: Expose and use the end of the physical memory address space" (LP: #2080563) - x86/kaslr: Expose and use the end of the physical memory address space [ Ubuntu: 5.15.0-125.135 ] * jammy/linux: 5.15.0-125.135 -proposed tracker (LP: #2083001) * CVE-2024-26800 - tls: rx: coalesce exit paths in tls_decrypt_sg() - tls: separate no-async decryption request handling from async - tls: fix use-after-free on failed backlog decryption * Please backport the more restrictive XSAVES deactivation for Zen1/2 arch (LP: #2077321) - x86/CPU/AMD: Improve the erratum 1386 workaround * Jammy update: v5.15.167 upstream stable release (LP: #2081279) - drm: panel-orientation-quirks: Add quirk for OrangePi Neo - ALSA: hda/generic: Add a helper to mute speakers at suspend/shutdown - ALSA: hda/conexant: Mute speakers at suspend / shutdown - i2c: Fix conditional for substituting empty ACPI functions - dma-debug: avoid deadlock between dma debug vs printk and netconsole - net: usb: qmi_wwan: add MeiG Smart SRM825L - drm/amdgpu: Fix uninitialized variable warning in amdgpu_afmt_acr - drm/amd/display: Assign linear_pitch_alignment even for VM - drm/amdgpu: fix overflowed array index read warning - drm/amdgpu/pm: Check the return value of smum_send_msg_to_smc - drm/amd/pm: fix uninitialized variable warning for smu8_hwmgr - drm/amd/pm: fix warning using uninitialized value of max_vid_step - drm/amd/pm: fix the Out-of-bounds read warning - drm/amdgpu: fix uninitialized scalar variable warning - drm/amd/pm: fix uninitialized variable warnings for vega10_hwmgr - drm/amdgpu: avoid reading vf2pf info size from FB - drm/amd/display: Check gpio_id before used as array index - drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 - drm/amd/display: Add array index check for hdcp ddc access - drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[] - drm/amd/display: Check msg_id before processing transcation - drm/amd/display: Fix Coverity INTEGER_OVERFLOW within dal_gpio_service_create - drm/amd/amdgpu: Check tbo resource pointer - drm/amdgpu/pm: Fix uninitialized variable warning for smu10 - drm/amdgpu/pm: Fix uninitialized variable agc_btc_response - drm/amdgpu: Fix out-of-bounds write warning - drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number - drm/amdgpu: fix ucode out-of-bounds read warning - drm/amdgpu: fix mc_data out-of-bounds read warning - drm/amdkfd: Reconcile the definition and use of oem_id in struct kfd_topology_device - apparmor: fix possible NULL pointer dereference - drm/amdgpu/pm: Check input value for CUSTOM profile mode setting on legacy SOCs - drm/amdgpu: fix the waring dereferencing hive - drm/amd/pm: check specific index for aldebaran - drm/amdgpu: the warning dereferencing obj for nbio_v7_4 - drm/amd/pm: check negtive return for table entries - drm/amdgpu: update type of buf size to u32 for eeprom functions - wifi: iwlwifi: remove fw_running op - cpufreq: scmi: Avoid overflow of target_freq in fast switch - PCI: al: Check IORESOURCE_BUS existence during probe - hwspinlock: Introduce hwspin_lock_bust() - RDMA/efa: Properly handle unexpected AQ completions - ionic: fix potential irq name truncation - rcu/nocb: Remove buggy bypass lock contention mitigation - usbip: Don't submit special requests twice - usb: typec: ucsi: Fix null pointer dereference in trace - fsnotify: clear PARENT_WATCHED flags lazily - smack: tcp: ipv4, fix incorrect labeling - drm/meson: plane: Add error handling - drm/bridge: tc358767: Check if fully initialized before signalling HPD event via IRQ - wifi: cfg80211: make hash table duplicates more survivable - block: remove the blk_flush_integrity call in blk_integrity_unregister - drm/amd/display: Skip wbscl_set_scaler_filter if filter is null - media: uvcvideo: Enforce alignment of frame and interval - drm/amd/pm: Fix the null pointer dereference for vega10_hwmgr - virtio_net: Fix napi_skb_cache_put warning - rcu-tasks: Fix show_rcu_tasks_trace_gp_kthread buffer overflow - ext4: reject casefold inode flag without casefold feature - udf: Limit file size to 4TB - ext4: handle redirtying in ext4_bio_write_page() - i2c: Use IS_REACHABLE() for substituting empty ACPI functions - sch/netem: fix use after free in netem_dequeue - ASoC: dapm: Fix UAF for snd_soc_pcm_runtime object - KVM: SVM: fix emulation of msr reads/writes of MSR_FS_BASE and MSR_GS_BASE - KVM: SVM: Don't advertise Bus Lock Detect to guest if SVM support is
[Bug 2080563] Re: Backport "x86/kaslr: Expose and use the end of the physical memory address space"
This bug was fixed in the package linux-gcp - 6.8.0-1017.19 --- linux-gcp (6.8.0-1017.19) noble; urgency=medium * noble/linux-gcp: 6.8.0-1017.19 -proposed tracker (LP: #2082407) * Don't produce linux-*-cloud-tools-common, linux-*-tools-common and linux-*-tools-host binary packages (LP: #2048183) - [Packaging]: gcp: Don't produce linux-*-cloud-tools-common, linux-*-tools- common and linux-*-tools-host binary packages * Remove obsolete build flags in derivative kernels (LP: #2077306) - [Packaging]: gcp: Remove obsolete build flags in derivative kernels * perf build disables tracepoint support (LP: #2076190) - [Packaging]: gcp: Add libtraceevent build depends as required by bd9b792a7740956f1c170fd55ab918172aa69be7 * sev-guest should be built-in (LP: #2083848) - [Config] Mark sev-guest as built-in * Backport "x86/kaslr: Expose and use the end of the physical memory address space" (LP: #2080563) - x86/kaslr: Expose and use the end of the physical memory address space * linux-gcp: mlx5_ib needed in the linux-modules package (LP: #2081891) - [Packaging] Move mlx5_ib module to linux-modules [ Ubuntu: 6.8.0-48.48 ] * noble/linux: 6.8.0-48.48 -proposed tracker (LP: #2082437) * [SRU][Noble] Bad EPP defaults cause performance regressions on select Intel CPUs (LP: #2077470) - x86/cpu/vfm: Update arch/x86/include/asm/intel-family.h - cpufreq: intel_pstate: Allow model specific EPPs - cpufreq: intel_pstate: Update default EPPs for Meteor Lake - cpufreq: intel_pstate: Switch to new Intel CPU model defines - cpufreq: intel_pstate: Update Meteor Lake EPPs - cpufreq: intel_pstate: Use Meteor Lake EPPs for Arrow Lake - cpufreq: intel_pstate: Update Balance performance EPP for Emerald Rapids * power: Enable intel_rapl driver (LP: #2078834) - powercap: intel_rapl: Add support for ArrowLake-H platform * x86/vmware: Add TDX hypercall support (LP: #2077729) - x86/vmware: Introduce VMware hypercall API - x86/vmware: Add TDX hypercall support * Guest crashes post migration with migrate_misplaced_folio+0x4cc/0x5d0 (LP: #2076866) - mm/mempolicy: use numa_node_id() instead of cpu_to_node() - mm/numa_balancing: allow migrate on protnone reference with MPOL_PREFERRED_MANY policy - mm: convert folio_estimated_sharers() to folio_likely_mapped_shared() - mm: factor out the numa mapping rebuilding into a new helper - mm: support multi-size THP numa balancing - mm/migrate: make migrate_misplaced_folio() return 0 on success - mm/migrate: move NUMA hinting fault folio isolation + checks under PTL - mm: fix possible OOB in numa_rebuild_large_mapping() * Add 'mm: hold PTL from the first PTE while reclaiming a large folio' to fix L2 Guest hang during LTP Test (LP: #2076147) - mm: hold PTL from the first PTE while reclaiming a large folio * KOP L2 guest fails to boot with 1 core - SMT8 topology (LP: #2070329) - KVM: PPC: Book3S HV nestedv2: Add DPDES support in helper library for Guest state buffer - KVM: PPC: Book3S HV nestedv2: Fix doorbell emulation * L2 Guest migration: continuously dumping while running NFS guest migration (LP: #2076406) - KVM: PPC: Book3S HV: Fix the set_one_reg for MMCR3 - KVM: PPC: Book3S HV: Fix the get_one_reg of SDAR - KVM: PPC: Book3S HV: Add one-reg interface for DEXCR register - KVM: PPC: Book3S HV nestedv2: Keep nested guest DEXCR in sync - KVM: PPC: Book3S HV: Add one-reg interface for HASHKEYR register - KVM: PPC: Book3S HV nestedv2: Keep nested guest HASHKEYR in sync - KVM: PPC: Book3S HV: Add one-reg interface for HASHPKEYR register - KVM: PPC: Book3S HV nestedv2: Keep nested guest HASHPKEYR in sync * perf build disables tracepoint support (LP: #2076190) - [Packaging] perf: reenable libtraceevent * Please backport the more restrictive XSAVES deactivation for Zen1/2 arch (LP: #2077321) - x86/CPU/AMD: Improve the erratum 1386 workaround * Fix alsa scarlett2 driver in 6.8 (LP: #2076402) - ALSA: scarlett2: Move initialisation code lower in the source - ALSA: scarlett2: Implement handling of the ACK notification * rtw89: reset IDMEM mode to prevent download firmware failure (LP: #2077396) - wifi: rtw89: 885xb: reset IDMEM mode to prevent download firmware failure * CVE-2024-43858 - jfs: Fix array-index-out-of-bounds in diFree * CVE-2024-42280 - mISDN: Fix a use after free in hfcmulti_tx() * CVE-2024-42271 - net/iucv: fix use after free in iucv_sock_close() * [Ubuntu-24.04] FADump with recommended crash size is making the L1 hang (LP: #2060039) - powerpc/64s/radix/kfence: map __kfence_pool at page granularity * Noble update: upstream stable patchset 2024-09-09 (LP: #2079945) - ocfs2: add bounds checking to ocfs2_check_dir_entry() - jfs: don't walk off the end of ealist - fs/ntfs3: Add a check for attr_name
[Bug 2080563] Re: Backport "x86/kaslr: Expose and use the end of the physical memory address space"
This bug was fixed in the package linux-gcp - 5.4.0-1139.148 --- linux-gcp (5.4.0-1139.148) focal; urgency=medium * focal/linux-gcp: 5.4.0-1139.148 -proposed tracker (LP: #2082913) * Packaging resync (LP: #1786013) - [Packaging] debian.gcp/dkms-versions -- update from kernel-versions (main/2024.09.30) * Backport "x86/kaslr: Expose and use the end of the physical memory address space" (LP: #2080563) - x86/kaslr: Expose and use the end of the physical memory address space * linux-gcp: Improve idle support (LP: #2080324) - cpuidle: Consolidate disabled state checks - cpuidle: Introduce cpuidle_driver_state_disabled() for driver quirks - cpuidle: Drop disabled field from struct cpuidle_state - ACPI: processor: Export function to claim _CST control - ACPI: processor: Introduce acpi_processor_evaluate_cst() - ACPI: processor: Clean up acpi_processor_evaluate_cst() - ACPI: processor: Make ACPI_PROCESSOR_CSTATE depend on ACPI_PROCESSOR - ACPI: processor: Export acpi_processor_evaluate_cst() - intel_idle: Refactor intel_idle_cpuidle_driver_init() - intel_idle: Use ACPI _CST for processor models without C-state tables - cpuidle: Allow idle states to be disabled by default - intel_idle: Allow ACPI _CST to be used for selected known processors - x86/cpu: Add Sapphire Rapids CPU model number - intel_idle: Fix max_cstate for processor models without C-state tables - intel_idle: add SPR support - SAUCE: x86/cpu: Add Emerald Rapids CPU model number - intel_idle: add Emerald Rapids Xeon support [ Ubuntu: 5.4.0-200.220 ] * focal/linux: 5.4.0-200.220 -proposed tracker (LP: #2082937) * Packaging resync (LP: #1786013) - [Packaging] debian.master/dkms-versions -- update from kernel-versions (main/2024.09.30) * CVE-2024-26800 - tls: rx: coalesce exit paths in tls_decrypt_sg() - tls: separate no-async decryption request handling from async - tls: fix use-after-free on failed backlog decryption * CVE-2024-26641 - ip6_tunnel: make sure to pull inner header in __ip6_tnl_rcv() * CVE-2021-47212 - net/mlx5: Update error handler for UCTX and UMEM * wbt:wbt_* trace event NULL pointer dereference with GENHD_FL_HIDDEN disks (LP: #2081085) - bdi: use bdi_dev_name() to get device name * Focal update: v5.4.284 upstream stable release (LP: #2081278) - drm: panel-orientation-quirks: Add quirk for OrangePi Neo - i2c: Fix conditional for substituting empty ACPI functions - net: usb: qmi_wwan: add MeiG Smart SRM825L - drm/amdgpu: Fix uninitialized variable warning in amdgpu_afmt_acr - drm/amdgpu: fix overflowed array index read warning - drm/amd/display: Check gpio_id before used as array index - drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 - drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[] - drm/amd/display: Fix Coverity INTEGER_OVERFLOW within dal_gpio_service_create - drm/amdgpu: fix ucode out-of-bounds read warning - drm/amdgpu: fix mc_data out-of-bounds read warning - drm/amdkfd: Reconcile the definition and use of oem_id in struct kfd_topology_device - apparmor: fix possible NULL pointer dereference - ionic: fix potential irq name truncation - usbip: Don't submit special requests twice - usb: typec: ucsi: Fix null pointer dereference in trace - smack: tcp: ipv4, fix incorrect labeling - wifi: cfg80211: make hash table duplicates more survivable - drm/amd/display: Skip wbscl_set_scaler_filter if filter is null - media: uvcvideo: Enforce alignment of frame and interval - block: initialize integrity buffer to zero before writing it to media - net: set SOCK_RCU_FREE before inserting socket into hashtable - virtio_net: Fix napi_skb_cache_put warning - udf: Limit file size to 4TB - i2c: Use IS_REACHABLE() for substituting empty ACPI functions - sch/netem: fix use after free in netem_dequeue - ASoC: dapm: Fix UAF for snd_soc_pcm_runtime object - ALSA: hda/conexant: Add pincfg quirk to enable top speakers on Sirius devices - ata: libata: Fix memory leak for error path in ata_host_alloc() - irqchip/gic-v2m: Fix refcount leak in gicv2m_of_init() - mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K - mmc: sdhci-of-aspeed: fix module autoloading - fuse: update stats for pages in dropped aux writeback list - fuse: use unsigned type for getxattr/listxattr size truncation - reset: hi6220: Add support for AO reset controller - clk: hi6220: use CLK_OF_DECLARE_DRIVER - clk: qcom: clk-alpha-pll: Fix the pll post div mask - clk: qcom: clk-alpha-pll: Fix the trion pll postdiv set rate API - ila: call nf_unregister_net_hooks() sooner - sched: sch_cake: fix bulk flow accounting logic for host fairness - nilfs2: fix missing cleanup on rollforward recovery error
[Bug 2080563] Re: Backport "x86/kaslr: Expose and use the end of the physical memory address space"
Boot testing passed on focal/jammy/noble gcp kernels. ** Tags removed: verification-needed-focal-linux-gcp verification-needed-jammy-linux-gcp verification-needed-noble-linux-gcp ** Tags added: verification-done-focal-linux-gcp verification-done-jammy-linux-gcp verification-done-noble-linux-gcp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080563 Title: Backport "x86/kaslr: Expose and use the end of the physical memory address space" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2080563/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080563] Re: Backport "x86/kaslr: Expose and use the end of the physical memory address space"
This bug is awaiting verification that the linux-gcp/6.8.0-1017.19 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-noble-linux-gcp' to 'verification-done-noble- linux-gcp'. If the problem still exists, change the tag 'verification- needed-noble-linux-gcp' to 'verification-failed-noble-linux-gcp'. 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: kernel-spammed-noble-linux-gcp-v2 verification-needed-noble-linux-gcp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080563 Title: Backport "x86/kaslr: Expose and use the end of the physical memory address space" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2080563/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080563] Re: Backport "x86/kaslr: Expose and use the end of the physical memory address space"
This bug is awaiting verification that the linux-gcp/5.15.0-1071.79 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-jammy-linux-gcp' to 'verification-done-jammy- linux-gcp'. If the problem still exists, change the tag 'verification- needed-jammy-linux-gcp' to 'verification-failed-jammy-linux-gcp'. 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: kernel-spammed-jammy-linux-gcp-v2 verification-needed-jammy-linux-gcp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080563 Title: Backport "x86/kaslr: Expose and use the end of the physical memory address space" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2080563/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080563] Re: Backport "x86/kaslr: Expose and use the end of the physical memory address space"
This bug is awaiting verification that the linux-gcp/5.4.0-1139.148 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-focal-linux-gcp' to 'verification-done-focal- linux-gcp'. If the problem still exists, change the tag 'verification- needed-focal-linux-gcp' to 'verification-failed-focal-linux-gcp'. 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: kernel-spammed-focal-linux-gcp-v2 verification-needed-focal-linux-gcp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080563 Title: Backport "x86/kaslr: Expose and use the end of the physical memory address space" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2080563/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080563] Re: Backport "x86/kaslr: Expose and use the end of the physical memory address space"
** Changed in: linux-gcp (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: linux-gcp (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-gcp (Ubuntu Noble)
Status: In Progress => Fix Committed
** Description changed:
[Impact]
Request from Google to backport "x86/kaslr: Expose and use the end of the
physical memory address space" to address intermittent CUDA hangs.
[Fix]
ea72ce5da22806d5713f3ffb39a6d5ae73841f93 ("x86/kaslr: Expose and use the end
of the physical memory address space")
[Test]
-
+ Compile and boot tested.
[Where problems could occur]
The fix directly affects memory management in x86 systems, specifically when
KASLR
is enabled.
[Other info]
#SF 00395854
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080563
Title:
Backport "x86/kaslr: Expose and use the end of the physical memory
address space"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2080563/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080563] Re: Backport "x86/kaslr: Expose and use the end of the physical memory address space"
** Changed in: linux-gcp (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Focal) Assignee: (unassigned) => Magali Lemes do Sacramento (magalilemes) ** Changed in: linux-gcp (Ubuntu Jammy) Assignee: (unassigned) => Magali Lemes do Sacramento (magalilemes) ** Changed in: linux-gcp (Ubuntu Noble) Assignee: (unassigned) => Magali Lemes do Sacramento (magalilemes) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080563 Title: Backport "x86/kaslr: Expose and use the end of the physical memory address space" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2080563/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080563] Re: Backport "x86/kaslr: Expose and use the end of the physical memory address space"
** Also affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080563 Title: Backport "x86/kaslr: Expose and use the end of the physical memory address space" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2080563/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080563] Re: Backport "x86/kaslr: Expose and use the end of the physical memory address space"
** Changed in: linux-gcp (Ubuntu) Assignee: (unassigned) => Magali Lemes do Sacramento (magalilemes) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080563 Title: Backport "x86/kaslr: Expose and use the end of the physical memory address space" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2080563/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
