[Bug 1907085] Re: Regression in backup-and-restore patch.
Launchpad Bug Tracker
1907085 at bugs.launchpad.net
Mon Jan 25 14:06:00 UTC 2021
This bug was fixed in the package grub2 - 2.04-1ubuntu26.8
---------------
grub2 (2.04-1ubuntu26.8) focal; urgency=medium
* debian/patches/grub-install-backup-and-restore.patch: Fix-up the patch
to correctly initialyze the names of the modules to restore. LP:
#1907085
* rhboot-f34-make-exit-take-a-return-code.patch,
rhboot-f34-dont-use-int-for-efi-status.patch: allow grub to exit
non-zero under EFI, this should allow falling back to the next
BootOrder BootEntry. LP: #1865515
* rhboot-f34-tcp-add-window-scaling-support.patch: speed up netboot
transfer speed. LP: #1911439
* rhboot-f34-support-non-ethernet.patch,
ubuntu-fixup-rhboot-f34-support-non-ethernet.patch,
ubuntu-fixup-rhboot-f34-support-non-ethernet-2.patch:
add support for link layer addresses of up to 32-bytes. LP: #1911439
* rhboot-f34-make-pmtimer-tsc-calibration-fast.patch:
speed up calibration time, especially when booting VMs. LP: #1911439
* minilzo: built using the distribution's minilzo. LP: #1911440
-- Dimitri John Ledkov <xnox at ubuntu.com> Wed, 13 Jan 2021 14:12:38
+0000
** Changed in: grub2 (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1907085
Title:
Regression in backup-and-restore patch.
Status in grub2 package in Ubuntu:
Fix Released
Status in grub2 source package in Bionic:
New
Status in grub2 source package in Focal:
Fix Released
Status in grub2 source package in Groovy:
Fix Released
Status in grub2 source package in Hirsute:
Fix Released
Bug description:
[Impact]
* A regression was identified in the backup & restore patch on some
architectures, which results in garbage filenames to be created in
/boot/grub.
The issue is reported on linux-ext4 mailing list https://marc.info/?l
=linux-ext4&m=160709231522785&w=2
[Test Case]
* Execute grub-install --target pc-i386 on i386 machine against a
nonexistent drive. Such that, backup & restore is triggered.
* Observe that the restored modules names in /boot/grub do not have
garbage file endings.
[Where problems could occur]
* The generated garbage file endings will remain on disk across
future upgrade and will need to be cleaned up manually. I am pondering
if I can clean them up somehow automatically. However the scope of the
affected machines should be very small and limited to i386.
[Other Info]
* Reported on linux-ext4 mailing list & debugged by / patch provided by colin watson.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1907085/+subscriptions
More information about the foundations-bugs
mailing list