debian/rules editconfigs does not work on s390x to change s390x only configs

Bug #1863116 reported by Frank Heimes
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Ubuntu on IBM z Systems
Fix Released
Undecided
Unassigned
linux (Ubuntu)
Fix Released
Undecided
Unassigned
Focal
Fix Released
Medium
Unassigned
Groovy
Fix Released
Undecided
Unassigned

Bug Description

SRU Justification:
==================

[Impact]

* With focal (and even eoan) it is no longer possible to run the updateconfigs Debian build rule (needed in case of kernel option updates) on all supported arhitectures.

* Changes upstream led to the fact cross platform functions are now triggered in case the config is changed, but amd64 is the only platform that has all needed crossbuild components to satisfy this.

* Hence one can still run updateconfigs on amd64 and proceed with the compile on the target platform.

* With bionic and earlier this was possible on all supported target platforms; now it only works on amd64.

* But it's not always the case that people who work on Ubuntu for non-amd64 have an Ubuntu amd64 on top, nor would such a requirement be acceptable.

[Fix]

* Patch: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1863116/+attachment/5397080/+files/0001-UBUNTU-Packaging-kernelconfig-only-update-edit-confi.patch

[Test Case]

* Setup an Ubuntu 20.04 on a platform other than amd64 (like in my case s390x) and install all packages needed for a kernel build.

* 'git clone' or 'pull-lp-source' the kernel sources to that system (e.g. focal).

* Change a kernel config option and run clean (fakeroot debian/rules clean), updateconfigs (fakeroot debian/rules updateconfigs) followed by a build (like: fakeroot debian/rules binary-headers binary-generic binary-perarch).

* Without the patch the build will fail with error messages similar to these:
   scripts/Kconfig.include:35: compiler 'x86_64-linux-gnu-gcc' not found
   make[3]: *** [../scripts/kconfig/Makefile:73: syncconfig] Error 1
   make[2]: *** [/home/ubuntu/linux-5.4-5.4.0/Makefile:594: syncconfig] Error 2
   make[2]: Leaving directory '/home/ubuntu/linux-5.4-5.4.0/build'
   make[1]: *** [Makefile:179: sub-make] Error 2
   make[1]: Leaving directory '/home/ubuntu/linux-5.4-5.4.0'
   make: *** [debian/rules.d/1-maintainer.mk:44: editconfigs] Error 2

* Doing the same on a non-amd64 with the patch in place (or on amd64 even w/o the patch), the build will succeed.

[Regression Potential]

* The regression risk is moderate since it's build time problem (not at kernel run time).

* But anyway in case this patch is broken, kernel builds may be screwed up entirely,

* but that is very unlikely since the modifications are limited to /debian/scripts/misc/kernelconfig.

* Hence issues in kernelconfig could occur and even break updateconfigs on amd64.

* But the patch was successully tested on different architectures with focal.

[Other]

* Patch need to be applied to focal and higher (hence incl. groovy).
__________

On s390x

pull-lp-source linux-5.4
cd linux-*
fakeroot ./debian/rules clean
./debian/rules editconfig
dh_testdir;
/bin/bash -e debian/scripts/misc/kernelconfig editconfigs
Do you want to edit config: amd64/config.flavour.generic? [Y/n] n
...
scripts/Kconfig.include:35: compiler 'x86_64-linux-gnu-gcc' not found
make[3]: *** [../scripts/kconfig/Makefile:73: syncconfig] Error 1
make[2]: *** [/home/ubuntu/linux-5.4-5.4.0/Makefile:594: syncconfig] Error 2
make[2]: Leaving directory '/home/ubuntu/linux-5.4-5.4.0/build'
make[1]: *** [Makefile:179: sub-make] Error 2
make[1]: Leaving directory '/home/ubuntu/linux-5.4-5.4.0'
make: *** [debian/rules.d/1-maintainer.mk:44: editconfigs] Error 2

And indeed i do not have x86_64-linux-gnu-gcc crosscompiler available to build on s390x for amd64, and also I don't want to touch amd64 configs. Only s390x ones.

As a user, I should be able to rebuild ports architecture kernel with tweaked config for testing, self-hosted without cross-compilers.

Frank Heimes (fheimes)
tags: added: focal rls-ff-incoming
removed: ff
description: updated
tags: added: champagne
summary: - crossbuild-essential-amd64 not installable on focal/s390x
+ debian/rules editconfigs does not work on s390x to change s390x only
+ configs
no longer affects: build-essential (Ubuntu)
Frank Heimes (fheimes)
tags: added: s390x
Revision history for this message
Matthias Klose (doko) wrote :

currently we don't build any cross compilers on s390x. Is this a scenario which is needed?
We do that on ppc64el, given that you actually can buy even some workstations.
and if needed, which targets should be supported?

Changed in ubuntu-z-systems:
status: New → Incomplete
Revision history for this message
Frank Heimes (fheimes) wrote :

Let me provide some more background on this (getting some lines back from the initial bug description):

On an (as of today) updated focal installation (on s390x) I needed to install the crossbuild-essential-amd64 package, but it's not installable and it seems to be the same for all "crossbuild-essential-*" packages. It's btw. the same on Eoan, too.

Now, I ran into this because I want to do a kernel test compile with a modified kernel option. If one modifies a kernel option, "fakeroot debian/rules updateconfigs" needs to be called.
I was told by the kernel team that at some point in time (somewhere between bionic and eoan) CROSS_COMPILE setting became needed to address architecture-dependent tests in Kconfig options. Hence cross toolchains are now required.
At least amd64 is needed, I don't know yet if more is needed (but I assume it's more).

Right now - as workaround - I need to do the kernel config changes on my local amd64 workstation run updateconfigs and can then proceed with build and test on the s390x target platform.

But it must be possible to prepare and compile a kernel with a modified kernel option on a single target platform.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

No, we must not require cross-compilers to all ubuntu kernel supported architectures to change a config of just one arch.

Ubuntu kernel build machinery must provide a way to rebuild a single arch kernel with different options without rebuilding configs of all other arches.

Please seek help from kernel team on how to tweak single arch config without cross compilers to all other arches.

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1863116

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: Incomplete → Confirmed
Revision history for this message
Frank Heimes (fheimes) wrote :

Looks like things got even worse now - currently I get:

$ DEB_BUILD_OPTIONS=parallel=8 AUTOBUILD=1 NOEXTRAS=1 fakeroot debian/rules binary-headers binary-generic binary-perarch
...
  CC [M] kernel/kheaders.o
make[2]: Leaving directory '/home/ubuntu/focal-lp1874057/debian/build/build-generic'
make[1]: *** [Makefile:179: sub-make] Error 2
make[1]: Leaving directory '/home/ubuntu/focal-lp1874057'
make: *** [debian/rules.d/2-binary-arch.mk:50: /home/ubuntu/focal-lp1874057/debian/stamps/stamp-build-generic] Error 2

I want to make sure that it's not my messy and I will do reset it up just to double check ...

Revision history for this message
Frank Heimes (fheimes) wrote :

$ DEB_BUILD_OPTIONS=parallel=8 AUTOBUILD=1 NOEXTRAS=1 fakeroot debian/rules binary-headers binary-generic
...
make[2]: Leaving directory '/home/ubuntu/focal-lp1874057/debian/build/build-generic'
make[1]: *** [Makefile:179: sub-make] Error 2
make[1]: Leaving directory '/home/ubuntu/focal-lp1874057'
make: *** [debian/rules.d/2-binary-arch.mk:50: /home/ubuntu/focal-lp1874057/debian/stamps/stamp-build-generic] Error 2

$ cat Makefile | sed -n '179p'
 $(Q)$(MAKE) -C $(abs_objtree) -f $(abs_srctree)/Makefile $(MAKECMDGOALS)
$ cat debian/rules.d/2-binary-arch.mk | sed -n '50p'
 $(build_cd) $(kmake) $(build_O) $(conc_level) $(bldimg) modules $(if $(filter true,$(do_dtbs)),dtbs)

Changed in linux-5.4 (Ubuntu):
status: New → Invalid
no longer affects: linux-5.4 (Ubuntu)
Revision history for this message
Robert Henry (mhodog) wrote :

Running on an arm64 build machine,
I checked out from
  git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal
the branch
  HEAD detached at Ubuntu-5.4.0-39.43
and follow the instructions at
  https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel#Modifying_the_configuration
and find that it iterates through all target machines, and requires that each target's cross compiler to be installed correctly.

So from my perspective, working as close as possible to head, I still see the same problems

I don't know why this was marked 'invalid'.

Revision history for this message
Jiandi An (jiandi) wrote :

Same here. Why is this changed from New to Invalid?

On arm64 system,
Checking out this https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7.10/

cod/mainline/v5.7.10 (d4563ab7fb2d4e8303c493a4eaa34e0189843e5b)
git://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack cod/mainline/v5.7.10

Following instructions at https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel#Modifying_the_configuration

fakeroot debian/rules editconfigs always assumes amd64 and no matter answering Y or N to the first question it pops up "Do you want to edit config: amd64/config.flavour.generic?", it'll always fail saying scripts/Kconfig.include:45: compiler 'x86_64-linux-gnu-gcc' not found.

How to editconfig for arm64 kernel? I'm building kernel natively on an arm64 machine.

$ LANG=C fakeroot debian/rules editconfigs
/bin/bash: /home/cuda/jiandi/sb/v5.7.10/mainline-crack/debian.master/abi/5.7.10-0.0/arm64/../modules.ignore: No such file or directory
dh_testdir;
/bin/bash -e debian/scripts/misc/kernelconfig editconfigs
Do you want to edit config: amd64/config.flavour.generic? [Y/n] n
make[1]: Entering directory '/home/cuda/jiandi/sb/v5.7.10/mainline-crack'
make[2]: Entering directory '/home/cuda/jiandi/sb/v5.7.10/mainline-crack/build'
  GEN Makefile
  HOSTCC scripts/basic/fixdep
  HOSTCC scripts/kconfig/conf.o
  HOSTCC scripts/kconfig/confdata.o
  HOSTCC scripts/kconfig/expr.o
  LEX scripts/kconfig/lexer.lex.c
  YACC scripts/kconfig/parser.tab.[ch]
  HOSTCC scripts/kconfig/lexer.lex.o
  HOSTCC scripts/kconfig/parser.tab.o
  HOSTCC scripts/kconfig/preprocess.o
  HOSTCC scripts/kconfig/symbol.o
  HOSTCC scripts/kconfig/util.o
  HOSTLD scripts/kconfig/conf
scripts/kconfig/conf --syncconfig Kconfig
scripts/Kconfig.include:45: compiler 'x86_64-linux-gnu-gcc' not found
make[3]: *** [../scripts/kconfig/Makefile:71: syncconfig] Error 1
make[2]: *** [/home/cuda/jiandi/sb/v5.7.10/mainline-crack/Makefile:588: syncconfig] Error 2
make[2]: Leaving directory '/home/cuda/jiandi/sb/v5.7.10/mainline-crack/build'
make[1]: *** [Makefile:180: sub-make] Error 2
make[1]: Leaving directory '/home/cuda/jiandi/sb/v5.7.10/mainline-crack'
make: *** [debian/rules.d/1-maintainer.mk:48: editconfigs] Error 2

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Only "linux-5.4" task was changed to invalid before it was removed.
The "linux" task was and still is confirmed.

Launchpad bug tracker supports tracking multiple states across multiple packages simultaniously. You can always see the correct status of the bug, for each task, at the top of the page. It is currently confirmed.

Revision history for this message
Andy Whitcroft (apw) wrote :

Fundamentally you have to have a compiler to update the configuration on an architecture. We can however limit update/edit operations to the architectures for which appropriate compilers are available.

Attached is a patch implementing this exclusion. Could those affected try applying this to their tree and retry the operation. Please report any testing back here.

tags: added: patch
Revision history for this message
Frank Heimes (fheimes) wrote :

Thanks Andy, that worked fine for me.
I still had 'some' focal kernel git tree lying around on a s390x system, updated it,
ran 'fakeroot debian/rules updateconfigs' w/o the patch (neg. test) and it failed.
I then applied your patch to 'debian/scripts/misc/kernelconfig'
did a clean (just to be sure), and another updateconfigs and it worked!
(For paranoia reason I also completed an entire kernel compile afterwards, which was fine, too.)
Many thx - so successful verified ! 👍

Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Frank Heimes (fheimes) wrote :
Stefan Bader (smb)
Changed in linux (Ubuntu Groovy):
status: Triaged → Fix Committed
Changed in linux (Ubuntu Focal):
importance: Undecided → Medium
status: New → Triaged
Frank Heimes (fheimes)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (44.2 KiB)

This bug was fixed in the package linux - 5.8.0-20.21

---------------
linux (5.8.0-20.21) groovy; urgency=medium

  * groovy/linux: 5.8.0-20.21 -proposed tracker (LP: #1896668)

  * Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
    (LP: #1853277)
    - i2c: core: Call i2c_acpi_install_space_handler() before
      i2c_acpi_register_devices()

  * Enable LTR for endpoints behind VMD (LP: #1896598)
    - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD

  * Remove duplicated code in ip_defrag.sh of kselftests/net (LP: #1894062)
    - Revert "UBUNTU: SAUCE: selftests: net: ip_defrag: modprobe missing
      nf_defrag_ipv6 support"

  * [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after stress S3
    (LP: #1893914)
    - SAUCE: xhci: workaround for S3 issue on AMD SNPS 3.0 xHC

  * debian/rules editconfigs does not work on s390x to change s390x only configs
    (LP: #1863116)
    - [Packaging] kernelconfig -- only update/edit configurations on architectures
      we have compiler support

  * [Ubuntu 20.10] zPCI DMA tables and bitmap leak on hard unplug (PCI Event
    0x0304) (LP: #1896216)
    - s390/pci: fix leak of DMA tables on hard unplug

  * md: improve IO accounting (LP: #1891151)
    - md: improve io stats accounting

  * Groovy update: v5.8.10 upstream stable release (LP: #1896078)
    - ARM: OMAP2+: Fix an IS_ERR() vs NULL check in _get_pwrdm()
    - ARM: dts: logicpd-torpedo-baseboard: Fix broken audio
    - ARM: dts: logicpd-som-lv-baseboard: Fix broken audio
    - ARM: dts: logicpd-som-lv-baseboard: Fix missing video
    - regulator: push allocation in regulator_ena_gpio_request() out of lock
    - regulator: remove superfluous lock in regulator_resolve_coupling()
    - ARM: dts: socfpga: fix register entry for timer3 on Arria10
    - ARM: dts: omap5: Fix DSI base address and clocks
    - ARM: dts: ls1021a: fix QuadSPI-memory reg range
    - ARM: dts: imx7ulp: Correct gpio ranges
    - arm64: dts: imx: Add missing imx8mm-beacon-kit.dtb to build
    - ARM: dts: imx7d-zii-rmu2: fix rgmii phy-mode for ksz9031 phy
    - RDMA/rtrs-srv: Replace device_register with device_initialize and device_add
    - RDMA/rxe: Fix memleak in rxe_mem_init_user
    - RDMA/rxe: Drop pointless checks in rxe_init_ports
    - RDMA/rxe: Fix panic when calling kmem_cache_create()
    - RDMA/bnxt_re: Do not report transparent vlan from QP1
    - RDMA/bnxt_re: Fix the qp table indexing
    - RDMA/bnxt_re: Static NQ depth allocation
    - RDMA/bnxt_re: Fix driver crash on unaligned PSN entry address
    - RDMA/bnxt_re: Remove the qp from list only if the qp destroy succeeds
    - drm/sun4i: add missing put_device() call in sun8i_r40_tcon_tv_set_mux()
    - arm64: dts: imx8mq: Fix TMU interrupt property
    - drm/sun4i: Fix dsi dcs long write function
    - scsi: qla2xxx: Fix regression on sparc64
    - scsi: libsas: Set data_dir as DMA_NONE if libata marks qc as NODATA
    - drm/virtio: fix unblank
    - RDMA/core: Fix unsafe linked list traversal after failing to allocate CQ
    - RDMA/core: Fix reported speed and width
    - scsi: megaraid_sas: Don't call disable_irq from process IRQ poll
    - scsi: mpt3sas: Don'...

Changed in linux (Ubuntu Groovy):
status: Fix Committed → Fix Released
Frank Heimes (fheimes)
Changed in linux (Ubuntu Focal):
status: Triaged → In Progress
Changed in ubuntu-z-systems:
status: Confirmed → In Progress
Revision history for this message
Frank Heimes (fheimes) wrote :

Patch "UBUNTU: [Packaging] kernelconfig -- only update/edit configurations on architectures we have compiler support" c4baeb418d79 landed in focal master-next now, hence updating status to Fix Committed.

Changed in linux (Ubuntu Focal):
status: In Progress → Fix Committed
Changed in ubuntu-z-systems:
status: In Progress → Fix Committed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-focal
Revision history for this message
Frank Heimes (fheimes) wrote :

This is a bit different to verify, since it's kernel scripting and infrastructure rather than doing testing with the proposed kernel itself.
But I tested it on groovy in the past, so the same should apply now with focal ...

I created a fresh focal master-next clone on a s390x system, like this:
$ git clone https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal --branch master-next --single-branch focal-clean

I installed everything needed to build a kernel (in fact I used my already existing build system that is known to work).

$ fakeroot debian/rules clean
succeeds

$ fakeroot debian/rules updateconfigs
fails, with:

...
scripts/kconfig/conf --syncconfig Kconfig
scripts/Kconfig.include:35: compiler 'x86_64-linux-gnu-gcc' not found
make[3]: *** [../scripts/kconfig/Makefile:73: syncconfig] Error 1
make[2]: *** [/home/ubuntu/focal-master-next/Makefile:617: syncconfig] Error 2
make[2]: Leaving directory '/home/ubuntu/focal-master-next/build'
make[1]: *** [Makefile:179: sub-make] Error 2
make[1]: Leaving directory '/home/ubuntu/focal-master-next'
make: *** [debian/rules.d/1-maintainer.mk:48: updateconfigs] Error 2

This is the same w/o the patch.
Hence I tried to look the patch up:

$ git log --oneline --grep "kernelconfig -- only update/edit configurations on architectures we have compiler support"
6b7b30d9153f UBUNTU: [Packaging] kernelconfig -- only update/edit configurations on architectures we have compiler support

It seems to be there but untagged and 'ambiguous':

$ git tag --contains 6b7b30d9153f
warning: refname '6b7b30d9153f' is ambiguous.
6b7b30d9153f
6b7b30d9153ffc0cedfb1016b7c86edea1ec468c

Using the full hash I get the following output:

$ git show 6b7b30d9153ffc0cedfb1016b7c86edea1ec468c | head -n 8
warning: refname '6b7b30d9153ffc0cedfb1016b7c86edea1ec468c' is ambiguous.
Git normally never creates a ref that ends with 40 hex characters
because it will be ignored when you just specify 40-hex. These refs
may be created by mistake. For example,

  git switch -c $br $(git rev-parse ...)

where "$br" is somehow empty and a 40-hex ref is created. Please
examine these refs and maybe delete them. Turn this message off by
running "git config advice.objectNameWarning false"
commit 6b7b30d9153ffc0cedfb1016b7c86edea1ec468c
Author: Andy Whitcroft <email address hidden>
Date: Wed Aug 12 22:28:28 2020 +0100

    UBUNTU: [Packaging] kernelconfig -- only update/edit configurations on architectures we have compiler support

    We can only rebuild, edit, or update a configuration for an architecture
    nativly on that architecture or using a compatible cross-compiler for
$

Even if the commit is the refname is marked as ambiguous, it seems to be in...

On groovy updateconfigs (on a non-amd64 system, like s390x) works and seems to be properly tagged:
$ git tag --contains 9705125c876a3268d17562bb8e46f53dfb8e6580
9705125c876a
Ubuntu-5.8.0-20.21
...
Ubuntu-5.8.0-30.32

So I'm setting the tag 'verification-failed-focal' here, even if this is kernel infrastructure, hence it does NOT block the proposed kernel itself.

tags: added: verification-failed-focal
removed: verification-needed-focal
Revision history for this message
Frank Heimes (fheimes) wrote :

I have to update the verification status for focal.
I re-did everything from scratch and it worked now.
(Did it twice, just to be sure - there was either a problem in the git tree I used or s/t went wrong while I transferred the data to a s390x test system or a racy situation ...)

I can now confirm that 'updateconfigs' works on a focal master-next tree on a non-amd64 system (s390x was used):

$ fakeroot debian/rules updateconfigs
dh_testdir;
/bin/bash -e debian/scripts/misc/kernelconfig updateconfigs
WARNING: x86_64-linux-gnu-gcc not installed
Running splitconfig.pl for amd64
...
Creating stub configs ...
  processing config.common.arm64 ... done.
  processing config.common.amd64 ... done.
  processing config.common.armhf ... done.
  processing config.common.s390x ... done.
  processing config.common.i386 ... done.
  processing config.common.ppc64el ... done.

Running config-check for all configurations ...

check-config: /tmp/tmp.IkFhf0NTgn/CONFIGS/s390x-config.flavour.generic: loading config
check-config: /home/ubuntu/focal-master-next/debian.master/config/annotations loading annotations
check-config: 133/133 checks passed -- exit 0

WARNING: configuration operation applied only to a subset of architectures (skipped amd64 i386 armhf arm64 ppc64el)

rm -rf build
$

A subsequent kernel build completed fine.

(same output an behavior than with groovy)

Adjusting tag accordingly ...

tags: added: verification-done-focal
removed: verification-failed-focal
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (78.9 KiB)

This bug was fixed in the package linux - 5.4.0-56.62

---------------
linux (5.4.0-56.62) focal; urgency=medium

  * focal/linux: 5.4.0-56.62 -proposed tracker (LP: #1905300)

  * CVE-2020-4788
    - selftests/powerpc: rfi_flush: disable entry flush if present
    - powerpc/64s: flush L1D on kernel entry
    - powerpc/64s: flush L1D after user accesses
    - selftests/powerpc: entry flush test

linux (5.4.0-55.61) focal; urgency=medium

  * focal/linux: 5.4.0-55.61 -proposed tracker (LP: #1903175)

  * Update kernel packaging to support forward porting kernels (LP: #1902957)
    - [Debian] Update for leader included in BACKPORT_SUFFIX

  * Avoid double newline when running insertchanges (LP: #1903293)
    - [Packaging] insertchanges: avoid double newline

  * EFI: Fails when BootCurrent entry does not exist (LP: #1899993)
    - efivarfs: Replace invalid slashes with exclamation marks in dentries.

  * CVE-2020-14351
    - perf/core: Fix race in the perf_mmap_close() function

  * raid10: Block discard is very slow, causing severe delays for mkfs and
    fstrim operations (LP: #1896578)
    - md: add md_submit_discard_bio() for submitting discard bio
    - md/raid10: extend r10bio devs to raid disks
    - md/raid10: pull codes that wait for blocked dev into one function
    - md/raid10: improve raid10 discard request
    - md/raid10: improve discard request for far layout
    - dm raid: fix discard limits for raid1 and raid10
    - dm raid: remove unnecessary discard limits for raid10

  * Bionic: btrfs: kernel BUG at /build/linux-
    eTBZpZ/linux-4.15.0/fs/btrfs/ctree.c:3233! (LP: #1902254)
    - btrfs: drop unnecessary offset_in_page in extent buffer helpers
    - btrfs: extent_io: do extra check for extent buffer read write functions
    - btrfs: extent-tree: kill BUG_ON() in __btrfs_free_extent()
    - btrfs: extent-tree: kill the BUG_ON() in insert_inline_extent_backref()
    - btrfs: ctree: check key order before merging tree blocks

  * Ethernet no link lights after reboot (Intel i225-v 2.5G) (LP: #1902578)
    - igc: Add PHY power management control

  * Undetected Data corruption in MPI workloads that use VSX for reductions on
    POWER9 DD2.1 systems (LP: #1902694)
    - powerpc: Fix undetected data corruption with P9N DD2.1 VSX CI load emulation
    - selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load
      workaround

  * [20.04 FEAT] Support/enhancement of NVMe IPL (LP: #1902179)
    - s390: nvme ipl
    - s390: nvme reipl
    - s390/ipl: support NVMe IPL kernel parameters

  * uvcvideo: add mapping for HEVC payloads (LP: #1895803)
    - media: uvcvideo: Add mapping for HEVC payloads

  * Focal update: v5.4.73 upstream stable release (LP: #1902115)
    - ibmveth: Switch order of ibmveth_helper calls.
    - ibmveth: Identify ingress large send packets.
    - ipv4: Restore flowi4_oif update before call to xfrm_lookup_route
    - mlx4: handle non-napi callers to napi_poll
    - net: fec: Fix phy_device lookup for phy_reset_after_clk_enable()
    - net: fec: Fix PHY init after phy_reset_after_clk_enable()
    - net: fix pos incrementment in ipv6_route_seq_next
    - net/smc: fix valid DMBE buffer sizes
    - net...

Changed in linux (Ubuntu Focal):
status: Fix Committed → Fix Released
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.