EFI: Fails when BootCurrent entry does not exist
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| curtin (Ubuntu) | Status tracked in Hirsute | |||||
| Xenial |
Undecided
|
Unassigned | ||||
| Bionic |
Undecided
|
Unassigned | ||||
| Focal |
Undecided
|
Unassigned | ||||
| Groovy |
Undecided
|
Unassigned | ||||
| Hirsute |
Medium
|
Unassigned | ||||
| linux (Ubuntu) | Status tracked in Hirsute | |||||
| Xenial |
Medium
|
dann frazier | ||||
| Bionic |
Medium
|
dann frazier | ||||
| Focal |
Medium
|
dann frazier | ||||
| Groovy |
Medium
|
dann frazier | ||||
| Hirsute |
Medium
|
dann frazier | ||||
Bug Description
[Impact]
MAAS installs fail on systems that have EFI Variables that include a "/" in the name.
Split out of bug 1894217.
[Test Case]
Using an OVMF-based VM, create a boot variable with a "/" character. For example:
Shell> setvar FOO/BAR -guid 8ed72b3f-
Then, in Linux:
$ ls /sys/firmware/
ls: reading directory '/sys/firmware/
BootOrder-
ConIn-8be4df61-
ConOut-
ErrOut-
MTC-eb704011-
The Input/output error is the key symptom. See below to see how that percolates up to MAAS install failures.
[Regression Risk]
There's a very tiny chance that someone has written code that depends on an the -EIO error for some reason. It's hard to guess why such a script would do that.
CVE References
| dann frazier (dannf) wrote : | #1 |
| summary: |
- Fails when BootCurrent entry does not exist + EFI: Fails when BootCurrent entry does not exist |
| dann frazier (dannf) wrote : | #3 |
I'm also assuming a firmware bug here, but I need to consult the specification. If it is a clear firmware bug then I think plan A should certainly be to pressure the vendor to release a fix.
Either way, I think we're likely to run into users suffering from this issue for a while. I tend to see issues like this appear on one platform only to reappear on other platforms in the future. And even if there is a firmware solution, we can't expect users to always be running the latest and greatest firmware. I'd therefore propose that we try to detect the issue and warn users of the problem - maybe even linking to this bug.
| Ryan Harper (raharper) wrote : | #4 |
@Dann
OK. That sounds reasonable. For this issue, curtin can (and I think it makes sense) ignore a BootCurrent value if there is no corresponding entry; warn in the logs that it's missing, check your firmware, etc... and proceed if it can.
| Changed in curtin (Ubuntu): | |
| importance: | Undecided → Medium |
| status: | Incomplete → Confirmed |
| nb (nateybobo) wrote : | #5 |
@dann @ryan
RE: I'm also assuming a firmware bug here, but I need to consult the specification. If it is a clear firmware bug then I think plan A should certainly be to pressure the vendor to release a fix.
Is there a way we can verify that the firmware is the true issue? I have Dell R420's running the latest firmware and can assist with testing if you'd like. If this can't be fixed I'll be forced to completely move away from MAAS and find another solution for bare metal provisioning :(
I posted my issues in Discourse: https:/
| nb (nateybobo) wrote : | #6 |
@dann @ryan
FYI - I refreshed to Snap 2.9.0~beta6-
| Ryan Harper (raharper) wrote : | #7 |
@nb This issue is *slightly* different than the other bug related to missing BootCurrent value.
The previous bug which is fixed in curtin happens when the BootCurrent value is not present in the efibootmgr output.
This bug has a BootCurrent value, like 0003, however, the Entries provided by efibootmgr do not have one for 0003.
Here's the raw output from efibootmgr -v:
BootCurrent: 0003
Timeout: 10 seconds
BootOrder: 0003,0004,
This system has no boot entries; this is a firmware bug.
From the log file, after curtin adds an entry for Ubuntu we can see the boot entries look like this:
{
"current": "0003",
"timeout": "10 seconds",
"order": [
"0000"
],
"entries": {
"0000": {
"name": "ubuntu",
"path": "HD(1,GPT,
}
}
}
Current pointed entry '0003', however, the list of entries only contains '0000' (what curtin just installed). Then when curtin attempts to place the newly installed entry at the beginning of the BootOrder list, it fails when we run this command:
efibootmgr -o 0003,0000
Invalid BootOrder order entry value0003
efibootmgr: entry 0003 does not exist
The fix for this in curtin is to verify that BootCurrent points to an existing entry; if not, then we ignore the BootCurrent value.
| Ryan Harper (raharper) wrote : | #8 |
@Dann
For this firmware bug where we have missing entries; Have you ever booted this up and had efibootmgr show all of the entries?
Looking at this output here:
BootCurrent: 0003
Timeout: 10 seconds
BootOrder: 0000,0003,
Boot0000* ubuntu HD(1,GPT,
With my suggested change to ignore BootCurrent since it does not have a matching entry; curtin can at best put the new entry 0000 first in order (note this is already done by grub-install).
This does mean that the node will be lost from maas control since it is no longer PXE booting...
Is that acceptable?
| Changed in curtin (Ubuntu): | |
| status: | Confirmed → Incomplete |
| dann frazier (dannf) wrote : | #9 |
I tried to prove whether or not this is a firmware issue or, perhaps, a bug in efibootmgr or curtin's calling of it. I deployed an affected system w/ MAAS w/ init=/bin/bash on the cmdline, and was surprised to see that efibootmgr showed the full expected set of Boot variables. However, if I ssh'd in while MAAS was deploying, efibootmgr was missing some. Turns out this depends on which virtual file system efibootmgr is using.
efivarfs is commonly mounted under /sys/firmware/
$ ls /sys/firmware/
ls: reading directory '/sys/firmware/
Boot mode select-
Boot0000-
BootCurrent-
BootOptionSuppo
BootOrder-
If /sys/firmware/
$ ls /sys/firmware/
Boot mode select-
Boot0000-
Boot0001-
Boot0003-
Boot0004-
Boot0005-
Boot0006-
BootCurrent-
BootOptionSuppo
BootOrder-
With init=/bin/bash, efivarfs is not yet mounted, which is why I see the full set at that point.
So why are these variables not visible in efivarfs? And does the "Input/output error" ls reports have something to do with it?
strace shows that the -EIO is coming from a getdents64() call:
openat(AT_FDCWD, "/sys/firmware/
fstat(3, {st_mode=
getdents64(3, /* 65 entries */, 32768) = 4800
getdents64(3, 0x5625e2d36510, 32768) = -1 EIO (Input/output error)
I built a 5.10-rc1+ kernel to see if this is maybe a kernel but that was already fixed upstream.
Turns out, the issue goes away there:
$ ls /sys/firmware/
Boot mode select-
Boot0000-
Boot0001-
Boot0003-
Boot0004-
Boot0005-
Boot0006-
BootCurrent-
BootOptionSuppo
BootOrder-
I'm now trying to determine what changed in the kernel.
| Changed in linux (Ubuntu): | |
| status: | New → Triaged |
| dann frazier (dannf) wrote : | #10 |
Ah:
commit 336af6a4686d885
Author: Michael Schaller <email address hidden>
Date: Fri Sep 25 09:45:02 2020 +0200
efivarfs: Replace invalid slashes with exclamation marks in dentries.
Without this patch efivarfs_
their name if the respective EFI variable has slashes in its name. This in
turn causes EIO on getdents64, which prevents a complete directory listing
of /sys/firmware/
This patch replaces the invalid shlashes with exclamation marks like
kobject_
named dentries under /sys/firmware/
Signed-off-by: Michael Schaller <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Ard Biesheuvel <email address hidden>
| dann frazier (dannf) wrote : | #11 |
With the above patch applied, we can see the culprit directories:
$ sudo find /sys/firmware/
/sys/firmware/
/sys/firmware/
| dann frazier (dannf) wrote : | #12 |
Patch backport to stable:
https:/
| Changed in curtin (Ubuntu): | |
| status: | Incomplete → Invalid |
| Changed in linux (Ubuntu): | |
| assignee: | nobody → dann frazier (dannf) |
| Changed in linux (Ubuntu Groovy): | |
| status: | New → In Progress |
| Changed in linux (Ubuntu Focal): | |
| assignee: | nobody → dann frazier (dannf) |
| status: | New → In Progress |
| Changed in linux (Ubuntu Xenial): | |
| assignee: | nobody → dann frazier (dannf) |
| status: | New → In Progress |
| Changed in linux (Ubuntu Groovy): | |
| assignee: | nobody → dann frazier (dannf) |
| Changed in curtin (Ubuntu Groovy): | |
| status: | New → Invalid |
| Changed in curtin (Ubuntu Focal): | |
| status: | New → Invalid |
| Changed in curtin (Ubuntu Bionic): | |
| status: | New → Invalid |
| Changed in curtin (Ubuntu Xenial): | |
| status: | New → Invalid |
| Changed in linux (Ubuntu Bionic): | |
| assignee: | nobody → dann frazier (dannf) |
| status: | New → In Progress |
| Changed in linux (Ubuntu Hirsute): | |
| status: | Triaged → In Progress |
| Changed in linux (Ubuntu Hirsute): | |
| importance: | Undecided → Medium |
| Changed in linux (Ubuntu Xenial): | |
| importance: | Undecided → Medium |
| Changed in linux (Ubuntu Bionic): | |
| importance: | Undecided → Medium |
| Changed in linux (Ubuntu Focal): | |
| importance: | Undecided → Medium |
| Changed in linux (Ubuntu Groovy): | |
| importance: | Undecided → Medium |
| Changed in linux (Ubuntu Xenial): | |
| status: | In Progress → Fix Committed |
| Changed in linux (Ubuntu Bionic): | |
| status: | In Progress → Fix Committed |
| Changed in linux (Ubuntu Focal): | |
| status: | In Progress → Fix Committed |
| Changed in linux (Ubuntu Groovy): | |
| status: | In Progress → Fix Committed |
| description: | updated |
| description: | updated |
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-
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:/
| tags: | added: verification-needed-xenial |
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-
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:/
| tags: | added: verification-needed-bionic |
| tags: | added: verification-needed-focal |
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-
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:/
| tags: | added: verification-needed-groovy |
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-
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:/
| dann frazier (dannf) wrote : | #17 |
= focal verification =
ubuntu@ubuntu:~$ cat /proc/version
Linux version 5.4.0-55-generic (buildd@
ubuntu@ubuntu:~$ ls /sys/firmware/
FOO!BAR-
| description: | updated |
| tags: |
added: verification-done-focal removed: verification-needed-focal |
| dann frazier (dannf) wrote : | #18 |
= groovy verification =
ubuntu@ubuntu:~$ cat /proc/version
Linux version 5.8.0-30-generic (buildd@
ubuntu@ubuntu:~$ ls /sys/firmware/
FOO!BAR-
| description: | updated |
| Changed in linux (Ubuntu Hirsute): | |
| status: | In Progress → Fix Committed |
| tags: |
added: verification-done-groovy removed: verification-needed-groovy |
| dann frazier (dannf) wrote : | #19 |
= bionic verification =
ubuntu@ubuntu:~$ cat /proc/cmdline
BOOT_IMAGE=
ubuntu@ubuntu:~$ ls /sys/firmware/
FOO!BAR-
| tags: |
added: verification-done-bionic removed: verification-needed-bionic |
| dann frazier (dannf) wrote : | #20 |
= xenial verification -
ubuntu@ubuntu:~$ cat /proc/cmdline
BOOT_IMAGE=
ubuntu@ubuntu:~$ ls /sys/firmware/
FOO!BAR-
| tags: |
added: verification-done-xenial removed: verification-needed-xenial |
| Launchpad Janitor (janitor) wrote : | #21 |
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_
- 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/
- 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_
- btrfs: extent-tree: kill the BUG_ON() in insert_
- 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_
- net: fec: Fix PHY init after phy_reset_
- 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 |
| Launchpad Janitor (janitor) wrote : | #22 |
This bug was fixed in the package linux - 4.4.0-197.229
---------------
linux (4.4.0-197.229) xenial; urgency=medium
* xenial/linux: 4.4.0-197.229 -proposed tracker (LP: #1905489)
* sha1_ce and sha2_ce modules no longer load on arm64 (LP: #1905336)
- SAUCE: Revert "crypto: arm64/sha - avoid non-standard inline asm tricks"
* Fails to build on powerpc (LP: #1905475)
- powerpc/
- SAUCE: powerpc/uaccess: only include kup-radix.h on PPC_BOOK3S_64
linux (4.4.0-196.228) xenial; urgency=medium
* xenial/linux: 4.4.0-196.228 -proposed tracker (LP: #1905309)
* CVE-2020-4788
- SAUCE: powerpc/64s: Define MASKABLE_
- SAUCE: powerpc/64s: move some exception handlers out of line
- powerpc/64s: flush L1D on kernel entry
- SAUCE: powerpc: Add a framework for user access tracking
- powerpc: Implement user_access_begin and friends
- powerpc: Fix __clear_user() with KUAP enabled
- powerpc/uaccess: Evaluate macro arguments once, before user access is
allowed
- powerpc/64s: flush L1D after user accesses
linux (4.4.0-195.227) xenial; urgency=medium
* xenial/linux: 4.4.0-195.227 -proposed tracker (LP: #1903107)
* 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
* CVE-2020-25645
- geneve: add transport ports in route lookup for geneve
* Xenial update: v4.4.241 upstream stable release (LP: #1902097)
- ibmveth: Identify ingress large send packets.
- tipc: fix the skb_unshare() in tipc_buf_append()
- net/ipv4: always honour route mtu during forwarding
- r8169: fix data corruption issue on RTL8402
- ALSA: bebob: potential info leak in hwdep_read()
- mm/kasan: print name of mem[set,cpy,move]() caller in report
- mm/kasan: add API to check memory regions
- compiler.h, kasan: Avoid duplicating __read_
- compiler.h: Add read_word_
- lib/strscpy: Shut up KASAN false-positives in strscpy()
- x86/mm/ptdump: Fix soft lockup in page table walker
- net: hdlc: In hdlc_rcv, check to make sure dev is an HDLC device
- net: hdlc_raw_eth: Clear the IFF_TX_SKB_SHARING flag after calling
ether_setup
- nfc: Ensure presence of NFC_ATTR_
nfc_
- tcp: fix to update snd_wl1 in bulk receiver fast path
- icmp: randomize the global rate limiter
- cifs: remove bogus debug code
- ima: Don't ignore errors from crypto_
- EDAC/i5100: Fix error handling order in i5100_init_one()
- crypto: ixp4xx - Fix the size used in a 'dma_free_
- media: Revert "media: exynos4-is: Add missed check for
pinctrl_
...
| Changed in linux (Ubuntu Xenial): | |
| status: | Fix Committed → Fix Released |
| Launchpad Janitor (janitor) wrote : | #23 |
This bug was fixed in the package linux - 5.8.0-31.33
---------------
linux (5.8.0-31.33) groovy; urgency=medium
* groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)
* Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
- drm/i915: Mark ininitial fb obj as WT on eLLC machines to avoid rcu lockup
during fbdev init
* 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.8.0-30.32) groovy; urgency=medium
* groovy/linux: 5.8.0-30.32 -proposed tracker (LP: #1903194)
* 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.
* raid10: Block discard is very slow, causing severe delays for mkfs and
fstrim operations (LP: #1896578)
- md: add md_submit_
- 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/
- btrfs: extent_io: do extra check for extent buffer read write functions
- btrfs: extent-tree: kill BUG_ON() in __btrfs_
- btrfs: extent-tree: kill the BUG_ON() in insert_
- btrfs: ctree: check key order before merging tree blocks
* Tiger Lake PMC core driver fixes (LP: #1899883)
- platform/x86: intel_pmc_core: update TGL's LPM0 reg bit map name
- platform/x86: intel_pmc_core: fix bound check in pmc_core_
- platform/x86: pmc_core: Use descriptive names for LPM registers
- platform/x86: intel_pmc_core: Fix TigerLake power gating status map
- platform/x86: intel_pmc_core: Fix the slp_s0 counter displayed value
* drm/i915/dp_mst - System would hang during the boot up. (LP: #1902469)
- Revert "UBUNTU: SAUCE: drm/i915/display: Fix null deref in
intel_
- drm/i915: Fix encoder lookup during PSR atomic check
* 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/ipl: support NVMe IPL kernel parameters
* uvcvideo: add mapping for HEVC payloads (LP: #1895803)
- media: uvcvideo: Add mapping for HEVC payloads
* risc-v 5.8 ...
| Changed in linux (Ubuntu Groovy): | |
| status: | Fix Committed → Fix Released |
| Launchpad Janitor (janitor) wrote : | #24 |
This bug was fixed in the package linux - 4.15.0-126.129
---------------
linux (4.15.0-126.129) bionic; urgency=medium
* bionic/linux: 4.15.0-126.129 -proposed tracker (LP: #1905305)
* CVE-2020-4788
- SAUCE: powerpc/64s: Define MASKABLE_
- SAUCE: powerpc/64s: move some exception handlers out of line
- powerpc/64s: flush L1D on kernel entry
- SAUCE: powerpc: Add a framework for user access tracking
- powerpc: Implement user_access_begin and friends
- powerpc: Fix __clear_user() with KUAP enabled
- powerpc/uaccess: Evaluate macro arguments once, before user access is
allowed
- powerpc/64s: flush L1D after user accesses
linux (4.15.0-125.128) bionic; urgency=medium
* bionic/linux: 4.15.0-125.128 -proposed tracker (LP: #1903137)
* 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_
- 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
* Bionic: btrfs: kernel BUG at /build/linux-
eTBZpZ/
- btrfs: use offset_in_page instead of open-coding it
- btrfs: use BUG() instead of BUG_ON(1)
- 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_
- btrfs: extent-tree: kill the BUG_ON() in insert_
- btrfs: ctree: check key order before merging tree blocks
* Bionic update: upstream stable patchset 2020-11-04 (LP: #1902943)
- USB: gadget: f_ncm: Fix NDP16 datagram validation
- gpio: tc35894: fix up tc35894 interrupt configuration
- vsock/virtio: use RCU to avoid use-after-free on the_virtio_vsock
- vsock/virtio: stop workers during the .remove()
- vsock/virtio: add transport parameter to the
virtio_
- net: virtio_vsock: Enhance connection semantics
- Input: i8042 - add nopnp quirk for Acer Aspire 5 A515
- ftrace: Move RCU is watching check after recursion check
- drm/amdgpu: restore proper ref count in amdgpu_
- drivers/
- drm/sun4i: mixer: Extend regmap max_register
- net: dec: de2104x: Increase receive ring size for Tulip
- rndis_host: increase sleep time in the query-response loop
- nvme-core: get/put ctrl ...
| Changed in linux (Ubuntu Bionic): | |
| status: | Fix Committed → Fix Released |
| Launchpad Janitor (janitor) wrote : | #25 |
This bug was fixed in the package linux - 5.8.0-36.40+21.04.1
---------------
linux (5.8.0-
* Packaging resync (LP: #1786013)
- update dkms package versions
[ Ubuntu: 5.8.0-36.40 ]
* debian/
(LP: #1878897)
- [Packaging] file-downloader not handling positive failures correctly
[ Ubuntu: 5.8.0-35.39 ]
* Packaging resync (LP: #1786013)
- update dkms package versions
* CVE-2021-1052 // CVE-2021-1053
- [Packaging] NVIDIA -- Add the NVIDIA 460 driver
-- Kleber Sacilotto de Souza <email address hidden> Thu, 07 Jan 2021 11:57:30 +0100
| Changed in linux (Ubuntu Hirsute): | |
| status: | Fix Committed → Fix Released |
Looking back at your patch:
Index: curtin-
=======
--- curtin-
+++ curtin-
@@ -886,6 +886,7 @@ def get_efibootmgr(
"""
with ChrootableTarge
stdout, _ = in_chroot.
+ LOG.info(
output = parse_efibootmg
return output
And the logs:
Running command ['unshare', '--fork', '--pid', '--', 'chroot', '/tmp/tmp6ha4_
DANNF:
BootCurrent: 0003
Timeout: 10 seconds
BootOrder: 0003,0004,
The firmware appears to have no entries at all; but somehow has a BootCurrent and a BootOrder pointing to entries that don't exist. This certainly has to be a firmware bug no?