[Kernel-packages] [Bug 1895109] Re: mm/slub kernel oops on focal kernel 5.4.0-45
This bug was fixed in the package linux - 5.8.0-21.22 --- linux (5.8.0-21.22) groovy; urgency=medium * groovy/linux: 5.8.0-21.22 -proposed tracker (LP: #1898150) * Packaging resync (LP: #1786013) - update dkms package versions * Fix broken e1000e device after S3 (LP: #1897755) - SAUCE: e1000e: Increase polling timeout on MDIC ready bit * EFA: add support for 0xefa1 devices (LP: #1896791) - RDMA/efa: Expose maximum TX doorbell batch - RDMA/efa: Expose minimum SQ size - RDMA/efa: User/kernel compatibility handshake mechanism - RDMA/efa: Add EFA 0xefa1 PCI ID * Groovy update: v5.8.13 upstream stable release (LP: #1898076) - device_cgroup: Fix RCU list debugging warning - ASoC: pcm3168a: ignore 0 Hz settings - ASoC: wm8994: Skip setting of the WM8994_MICBIAS register for WM1811 - ASoC: wm8994: Ensure the device is resumed in wm89xx_mic_detect functions - ASoC: Intel: bytcr_rt5640: Add quirk for MPMAN Converter9 2-in-1 - clk: versatile: Add of_node_put() before return statement - RISC-V: Take text_mutex in ftrace_init_nop() - i2c: aspeed: Mask IRQ status to relevant bits - s390/init: add missing __init annotations - lockdep: fix order in trace_hardirqs_off_caller() - EDAC/ghes: Check whether the driver is on the safe list correctly - drm/amdkfd: fix a memory leak issue - drm/amd/display: Don't use DRM_ERROR() for DTM add topology - drm/amd/display: update nv1x stutter latencies - drm/amdgpu/dc: Require primary plane to be enabled whenever the CRTC is - drm/amd/display: Don't log hdcp module warnings in dmesg - objtool: Fix noreturn detection for ignored functions - i2c: mediatek: Send i2c master code at more than 1MHz - riscv: Fix Kendryte K210 device tree - ieee802154: fix one possible memleak in ca8210_dev_com_init - ieee802154/adf7242: check status of adf7242_read_reg - clocksource/drivers/h8300_timer8: Fix wrong return value in h8300_8timer_init() - batman-adv: bla: fix type misuse for backbone_gw hash indexing - libbpf: Fix build failure from uninitialized variable warning - atm: eni: fix the missed pci_disable_device() for eni_init_one() - batman-adv: mcast/TT: fix wrongly dropped or rerouted packets - netfilter: ctnetlink: add a range check for l3/l4 protonum - netfilter: ctnetlink: fix mark based dump filtering regression - netfilter: conntrack: nf_conncount_init is failing with IPv6 disabled - netfilter: nft_meta: use socket user_ns to retrieve skuid and skgid - mac802154: tx: fix use-after-free - bpf: Fix clobbering of r2 in bpf_gen_ld_abs - tools/libbpf: Avoid counting local symbols in ABI check - drm/vc4/vc4_hdmi: fill ASoC card owner - net: qed: Disable aRFS for NPAR and 100G - net: qede: Disable aRFS for NPAR and 100G - net: qed: RDMA personality shouldn't fail VF load - igc: Fix wrong timestamp latency numbers - igc: Fix not considering the TX delay for timestamps - drm/sun4i: sun8i-csc: Secondary CSC register correction - hv_netvsc: Switch the data path at the right time during hibernation - spi: spi-fsl-dspi: use XSPI mode instead of DMA for DPAA2 SoCs - RDMA/core: Fix ordering of CQ pool destruction - batman-adv: Add missing include for in_interrupt() - xsk: Fix number of pinned pages/umem size discrepancy - nvme-tcp: fix kconfig dependency warning when !CRYPTO - batman-adv: mcast: fix duplicate mcast packets in BLA backbone from LAN - batman-adv: mcast: fix duplicate mcast packets in BLA backbone from mesh - batman-adv: mcast: fix duplicate mcast packets from BLA backbone to mesh - bpf: Fix a rcu warning for bpffs map pretty-print - lib80211: fix unmet direct dependendices config warning when !CRYPTO - mac80211: do not disable HE if HT is missing on 2.4 GHz - cfg80211: fix 6 GHz channel conversion - mac80211: fix 80 MHz association to 160/80+80 AP on 6 GHz - ALSA: asihpi: fix iounmap in error handler - io_uring: fix openat/openat2 unified prep handling - SUNRPC: Fix svc_flush_dcache() - regmap: fix page selection for noinc reads - regmap: fix page selection for noinc writes - net/mlx5e: mlx5e_fec_in_caps() returns a boolean - MIPS: Loongson-3: Fix fp register access if MSA enabled - PM / devfreq: tegra30: Disable clock on error in probe - MIPS: Add the missing 'CPU_1074K' into __get_cpu_type() - regulator: axp20x: fix LDO2/4 description - spi: bcm-qspi: Fix probe regression on iProc platforms - KVM: x86: Reset MMU context if guest toggles CR4.SMAP or CR4.PKE - KVM: SVM: Add a dedicated INVD intercept routine - mm: validate pmd after splitting - arch/x86/lib/usercopy_64.c: fix __copy_user_flushcache() cache writeback - x86/irq: Make run_on_irqstack_cond() typesafe - x86/ioapic: Unbreak check_timer() - scsi: lpfc: Fix initial FLOGI failure due to BBSCN
[Kernel-packages] [Bug 1895109] Re: mm/slub kernel oops on focal kernel 5.4.0-45
This bug was fixed in the package linux - 5.4.0-48.52 --- linux (5.4.0-48.52) focal; urgency=medium * focal/linux: 5.4.0-48.52 -proposed tracker (LP: #1894654) * mm/slub kernel oops on focal kernel 5.4.0-45 (LP: #1895109) - SAUCE: Revert "mm/slub: fix a memory leak in sysfs_slab_add()" * Packaging resync (LP: #1786013) - update dkms package versions - update dkms package versions * Introduce the new NVIDIA 450-server and the 450 UDA series (LP: #1887674) - [packaging] add signed modules for nvidia 450 and 450-server * [UBUNTU 20.04] zPCI attach/detach issues with PF/VF linking support (LP: #1892849) - s390/pci: fix zpci_bus_link_virtfn() - s390/pci: re-introduce zpci_remove_device() - s390/pci: fix PF/VF linking on hot plug * [UBUNTU 20.04] kernel: s390/cpum_cf,perf: changeDFLT_CCERROR counter name (LP: #1891454) - s390/cpum_cf, perf: change DFLT_CCERROR counter name * [UBUNTU 20.04] zPCI: Enabling of a reserved PCI function regression introduced by multi-function support (LP: #1891437) - s390/pci: fix enabling a reserved PCI function * CVE-2020-12888 - vfio/type1: Support faulting PFNMAP vmas - vfio-pci: Fault mmaps to enable vma tracking - vfio-pci: Invalidate mmaps and block MMIO access on disabled memory * [Hyper-V] VSS and File Copy daemons intermittently fails to start (LP: #1891224) - [Packaging] Bind hv_vss_daemon startup to hv_vss device - [Packaging] bind hv_fcopy_daemon startup to hv_fcopy device * alsa/hdmi: support nvidia mst hdmi/dp audio (LP: #1867704) - ALSA: hda - Rename snd_hda_pin_sense to snd_hda_jack_pin_sense - ALSA: hda - Add DP-MST jack support - ALSA: hda - Add DP-MST support for non-acomp codecs - ALSA: hda - Add DP-MST support for NVIDIA codecs - ALSA: hda: hdmi - fix regression in connect list handling - ALSA: hda: hdmi - fix kernel oops caused by invalid PCM idx - ALSA: hda: hdmi - preserve non-MST PCM routing for Intel platforms - ALSA: hda: hdmi - Keep old slot assignment behavior for Intel platforms - ALSA: hda - Fix DP-MST support for NVIDIA codecs * Focal update: v5.4.60 upstream stable release (LP: #1892899) - smb3: warn on confusing error scenario with sec=krb5 - genirq/affinity: Make affinity setting if activated opt-in - genirq/PM: Always unlock IRQ descriptor in rearm_wake_irq() - PCI: hotplug: ACPI: Fix context refcounting in acpiphp_grab_context() - PCI: Add device even if driver attach failed - PCI: qcom: Define some PARF params needed for ipq8064 SoC - PCI: qcom: Add support for tx term offset for rev 2.1.0 - btrfs: allow use of global block reserve for balance item deletion - btrfs: free anon block device right after subvolume deletion - btrfs: don't allocate anonymous block device for user invisible roots - btrfs: ref-verify: fix memory leak in add_block_entry - btrfs: stop incremening log_batch for the log root tree when syncing log - btrfs: remove no longer needed use of log_writers for the log root tree - btrfs: don't traverse into the seed devices in show_devname - btrfs: open device without device_list_mutex - btrfs: move the chunk_mutex in btrfs_read_chunk_tree - btrfs: relocation: review the call sites which can be interrupted by signal - btrfs: add missing check for nocow and compression inode flags - btrfs: avoid possible signal interruption of btrfs_drop_snapshot() on relocation tree - btrfs: sysfs: use NOFS for device creation - btrfs: don't WARN if we abort a transaction with EROFS - btrfs: fix race between page release and a fast fsync - btrfs: fix messages after changing compression level by remount - btrfs: only search for left_info if there is no right_info in try_merge_free_space - btrfs: inode: fix NULL pointer dereference if inode doesn't need compression - btrfs: fix memory leaks after failure to lookup checksums during inode logging - btrfs: make sure SB_I_VERSION doesn't get unset by remount - btrfs: fix return value mixup in btrfs_get_extent - arm64: perf: Correct the event index in sysfs - dt-bindings: iio: io-channel-mux: Fix compatible string in example code - iio: dac: ad5592r: fix unbalanced mutex unlocks in ad5592r_read_raw() - xtensa: add missing exclusive access state management - xtensa: fix xtensa_pmu_setup prototype - cifs: Fix leak when handling lease break for cached root fid - powerpc/ptdump: Fix build failure in hashpagetable.c - powerpc: Allow 4224 bytes of stack expansion for the signal frame - powerpc: Fix circular dependency between percpu.h and mmu.h - pinctrl: ingenic: Enhance support for IRQ_TYPE_EDGE_BOTH - media: vsp1: dl: Fix NULL pointer dereference on unbind - net: ethernet: stmmac: Disable hardware multicast filter - net: stmmac: dwmac1000: provide multicast filter fallback
[Kernel-packages] [Bug 1895109] Re: mm/slub kernel oops on focal kernel 5.4.0-45
Marking as verified, based on feedback we received on other channels. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1895109 Title: mm/slub kernel oops on focal kernel 5.4.0-45 Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: [ Impact ] As reported on bug 1894780 (Oops and hang when starting LVM snapshots on 5.4.0-47), some changes applied to focal/linux 5.4.0-45 introduced a regression likely on the mm/slub code. A fix hasn't been identified yet, however, reverting commit "mm/slub: fix a memory leak in sysfs_slab_add()", upstream dde3c6b72a16c2db826f54b2d49bdea26c3534a2, applied to focal/linux as part of v5.4.47 upstream stable release (bug 1884089), seems to improve the situation. [ Fix ] I propose to revert commit "mm/slub: fix a memory leak in sysfs_slab_add()" while we don't find a better fix for it. [ Test Case ] Please see bug 1894780. [ Regression potential ] The commit being reverted fixes a memory leak from a 2015 commit, so the chances of reverting it introducing more regressions is low. However, if it does we can expect issues on the sysfs slab code during memory allocations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895109/+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 1895109] Re: mm/slub kernel oops on focal kernel 5.4.0-45
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- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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-focal -- 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/1895109 Title: mm/slub kernel oops on focal kernel 5.4.0-45 Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: [ Impact ] As reported on bug 1894780 (Oops and hang when starting LVM snapshots on 5.4.0-47), some changes applied to focal/linux 5.4.0-45 introduced a regression likely on the mm/slub code. A fix hasn't been identified yet, however, reverting commit "mm/slub: fix a memory leak in sysfs_slab_add()", upstream dde3c6b72a16c2db826f54b2d49bdea26c3534a2, applied to focal/linux as part of v5.4.47 upstream stable release (bug 1884089), seems to improve the situation. [ Fix ] I propose to revert commit "mm/slub: fix a memory leak in sysfs_slab_add()" while we don't find a better fix for it. [ Test Case ] Please see bug 1894780. [ Regression potential ] The commit being reverted fixes a memory leak from a 2015 commit, so the chances of reverting it introducing more regressions is low. However, if it does we can expect issues on the sysfs slab code during memory allocations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895109/+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 1895109] Re: mm/slub kernel oops on focal kernel 5.4.0-45
I'm setting the 'Linux' task as 'Invalid' as the fix for the issue should be worked via bug 1894780. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- 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/1895109 Title: mm/slub kernel oops on focal kernel 5.4.0-45 Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: [ Impact ] As reported on bug 1894780 (Oops and hang when starting LVM snapshots on 5.4.0-47), some changes applied to focal/linux 5.4.0-45 introduced a regression likely on the mm/slub code. A fix hasn't been identified yet, however, reverting commit "mm/slub: fix a memory leak in sysfs_slab_add()", upstream dde3c6b72a16c2db826f54b2d49bdea26c3534a2, applied to focal/linux as part of v5.4.47 upstream stable release (bug 1884089), seems to improve the situation. [ Fix ] I propose to revert commit "mm/slub: fix a memory leak in sysfs_slab_add()" while we don't find a better fix for it. [ Test Case ] Please see bug 1894780. [ Regression potential ] The commit being reverted fixes a memory leak from a 2015 commit, so the chances of reverting it introducing more regressions is low. However, if it does we can expect issues on the sysfs slab code during memory allocations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895109/+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 1895109] Re: mm/slub kernel oops on focal kernel 5.4.0-45
** Changed in: linux (Ubuntu Focal) Status: Confirmed => 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/1895109 Title: mm/slub kernel oops on focal kernel 5.4.0-45 Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: [ Impact ] As reported on bug 1894780 (Oops and hang when starting LVM snapshots on 5.4.0-47), some changes applied to focal/linux 5.4.0-45 introduced a regression likely on the mm/slub code. A fix hasn't been identified yet, however, reverting commit "mm/slub: fix a memory leak in sysfs_slab_add()", upstream dde3c6b72a16c2db826f54b2d49bdea26c3534a2, applied to focal/linux as part of v5.4.47 upstream stable release (bug 1884089), seems to improve the situation. [ Fix ] I propose to revert commit "mm/slub: fix a memory leak in sysfs_slab_add()" while we don't find a better fix for it. [ Test Case ] Please see bug 1894780. [ Regression potential ] The commit being reverted fixes a memory leak from a 2015 commit, so the chances of reverting it introducing more regressions is low. However, if it does we can expect issues on the sysfs slab code during memory allocations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895109/+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
