Comment 31 for bug 1792575

Verification-done with the xenial grub2/grub2-signed versions:

$ dpkg -l grub\* | grep ii
ii grub-common 2.02~beta2-36ubuntu3.20 amd64 GRand Unified Bootloader (common files)
ii grub-efi-amd64 2.02~beta2-36ubuntu3.20 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 version)
ii grub-efi-amd64-bin 2.02~beta2-36ubuntu3.20 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 binaries)
ii grub-efi-amd64-signed 1.66.20+2.02~beta2-36ubuntu3.20 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 version, signed)
ii grub2-common 2.02~beta2-36ubuntu3.20 amd64 GRand Unified Bootloader (common files for version 2)

I am unable to accurately verify chainloading grub bootloaders from network to disk (especially as it appeared to be a hardware-dependent issue), however, I can easily verify the other side-effect of this, which would break chainloading Windows from grub. I was able to chainload Windows 10 just fine with the patches applied.

Given that this is the same two patches as applied in other releases that was applied without changes, and that they have also successfully passed validation for both chainloading Windows 10 and chainloading grub in Peter's environment (comment #21), I find this acceptable testing.