GitLab

The logic here is that if you are using native drivers it is probably because
there is a problem with the BIOS (e.g., the disk option ROM is not loaded--
why I went down this path in the first place!) And if there is a problem
with the BIOS, then any chain-booted grub is going to have the same issues
because it will probably be using the BIOS. So we just load the on-disk
grub.cfg directly, just like a chain-booted grub would have done. Lots of
potential problems here (e.g., on-disk grub is a different version,
residual state from our config file, etc.) but it seems to work.

This is an alternative to chainbooting through the partition bootblock.
The difference is that the chain-booted grub looks to be hardwired to use
the BIOS to read the disk. If the disk option ROM has not been loaded
(possible, since the current grub was loaded via PXE) this chainloaded
boot code will not work.

That's what Makefile will use and it is required if unusual flags
must be passed to linker (e.g. to build ppc32 code on ppc64le with clang).

Since btrfs on-disk format uses little-endian, the searched item types
(ROOT_REF, INODE_REF) need converting the byte order in order to
function properly on big-endian systems.

Found by: Coverity scan.
CID: 96651

Found by: Coverity scan.
CID: 96662, 96665

Found by: Coverity scan.
CID: 96671, 96658, 96653

Found by: Coverity scan.
CID: 96675

Found by: Coverity scan.
CID: 96676

Found by: Coverity scan.
CID: 96677

Found by: Coverity scan.
CID: 96678

Found by: Coverity scan.
CID: 96679

Found by: Coverity scan.
CID: 96682

Found by: Coverity scan.
CID: 96684

Found by: Coverity scan.
CID: 96685

Found by: Coverity scan.
CID: 96686

Found by: Coverity scan.
CID: 96688

Found by: Coverity scan.
CID: 96704

Found by: Coverity scan.
CID: 96706

Found by: Coverity scan.
CID: 96713

Found by: Coverity scan.
CID: 96714

Found by: Coverity scan.
CID: 96715

Found by: Coverity scan.
CID: 73772