device tree protocol not always applied
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
grub2 (Ubuntu) | ||||||
Focal |
Won't Fix
|
Undecided
|
Unassigned | |||
Jammy |
Won't Fix
|
Undecided
|
Unassigned | |||
Lunar |
Won't Fix
|
Undecided
|
Unassigned | |||
Mantic |
Fix Released
|
Undecided
|
Unassigned | |||
grub2-unsigned (Ubuntu) | Status tracked in Mantic | |||||
Focal |
Fix Released
|
Undecided
|
Mate Kukri | |||
Jammy |
Fix Released
|
Undecided
|
Mate Kukri | |||
Lunar |
Fix Released
|
Undecided
|
Mate Kukri | |||
Mantic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
device tree fixups are not applied when grub_fdt_load() has been called before, as that copies the device tree + extra space into a new fdt variable.
For example, when a pre-LoadFile2 kernel is being loaded, grub passes the initrd via device tree and needs to modify it, for which it calls the function. On pre-2.12 loaders, this happens for every kernel on arm64 as we do not support LoadFile2 there.
[Test plan]
Isaac has run the test to make sure the change works and Mate has verified that it doesn't regress qemu booting across a wide set of scenarios but either way we'd not block update releases on this but would rather reset the tasks after.
[Where problems could occur]
We're moving the fixup of the device tree to directly after loading it, so that grub can make any modifications to set initrd for example (there are no others yet), later.
Device tree fixup suddenly working can of course cause regressions if the fixups in u-boot are wrong.
Changed in grub2 (Ubuntu Focal): | |
assignee: | nobody → Mate Kukri (mkukri) |
Changed in grub2 (Ubuntu Jammy): | |
assignee: | nobody → Mate Kukri (mkukri) |
Changed in grub2 (Ubuntu Lunar): | |
assignee: | nobody → Mate Kukri (mkukri) |
Changed in grub2 (Ubuntu Mantic): | |
assignee: | nobody → Mate Kukri (mkukri) |
tags: | added: foundations-todo |
Changed in grub2 (Ubuntu Focal): | |
assignee: | Mate Kukri (mkukri) → nobody |
status: | New → Won't Fix |
Changed in grub2 (Ubuntu Jammy): | |
assignee: | Mate Kukri (mkukri) → nobody |
status: | New → Won't Fix |
Changed in grub2-unsigned (Ubuntu Mantic): | |
status: | New → Fix Released |
Changed in grub2 (Ubuntu Lunar): | |
assignee: | Mate Kukri (mkukri) → nobody |
status: | New → Won't Fix |
no longer affects: | grub2 (Ubuntu) |
Changed in grub2-unsigned (Ubuntu Lunar): | |
assignee: | nobody → Mate Kukri (mkukri) |
status: | New → Triaged |
Changed in grub2-unsigned (Ubuntu Jammy): | |
status: | New → Triaged |
Changed in grub2-unsigned (Ubuntu Focal): | |
status: | New → Triaged |
Changed in grub2-unsigned (Ubuntu Jammy): | |
assignee: | nobody → Mate Kukri (mkukri) |
Changed in grub2-unsigned (Ubuntu Focal): | |
assignee: | nobody → Mate Kukri (mkukri) |
description: | updated |
Changed in grub2-unsigned (Ubuntu Jammy): | |
status: | Triaged → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.