Hi Alex.
On Wed 14 Sep 08:34:47 2016, Alexander Graf wrote:
[...]
> Very nice catch!
Thanks!
[...]
> Can you please double-check that this is the only place the type
> mismatch happened?
So I skimmed through the boot and run-time service API implementations
and couldn't spot another
> On 13 Sep 2016, at 19:36, Robin Randhawa wrote:
>
> A type mismatch in the efi_allocate_pool boot service flow causes
> hazardous memory scribbling on 32-bit systems.
>
> This is efi_allocate_pool's prototype:
>
> static efi_status_t EFIAPI efi_allocate_pool(int
A type mismatch in the efi_allocate_pool boot service flow causes
hazardous memory scribbling on 32-bit systems.
This is efi_allocate_pool's prototype:
static efi_status_t EFIAPI efi_allocate_pool(int pool_type,
unsigned long size,
3 matches
Mail list logo