UEFI: Difference between revisions

1,010 bytes added ,  12 years ago
m
Started "Known Bugs"
[unchecked revision][unchecked revision]
No edit summary
m (Started "Known Bugs")
Line 272:
section '.reloc' fixups data discardable
</source>
 
 
== Known Firmware Bugs ==
 
For the memory management functions in EFI, an OS is meant to be able to use "memory type" values above 0x80000000 for its own purposes. In the OVFM EFI firmware release "r11337" (for Qemu, etc) there is a bug where the firmware assumes the memory type is within the range of values defined for EFI's own use, and uses the memory type as an array index. The end result is an "array index out of bounds" bug; where the higher memory type values (e.g. perfectly legal values above 0x80000000) cause the 64-bit version of the firmware to crash (page fault), and cause incorrect "attribute" values to be reported by the 32-bit version of the firmware. This same bug is also present in whatever version of the EFI firmware VirtualBox uses (which looks like an older version of OVFM); and I suspect (but don't know) that the bug may be present in a wide variety of firmware that was derived from the tianocore project (not just OVFM). [[User:Brendan|Brendan]] 15:30, 29 July 2011 (UTC)
 
 
== See also ==
250

edits