Re: [PATCH v5] Avoid crash calling PrintErrMesg from efi_multiboot2

2025-02-04 Thread Frediano Ziglio
On Tue, Feb 4, 2025 at 4:20 PM Andrew Cooper wrote: > > On 22/01/2025 10:14 am, Frediano Ziglio wrote: > > Although code is compiled with -fpic option data is not position > > independent. > > This doesn't parse. ITYM "Although the code is compiled with -fpic, > pointers in data are not position

Re: [PATCH v5] Avoid crash calling PrintErrMesg from efi_multiboot2

2025-02-04 Thread Andrew Cooper
On 22/01/2025 10:14 am, Frediano Ziglio wrote: > Although code is compiled with -fpic option data is not position > independent. This doesn't parse.  ITYM "Although the code is compiled with -fpic, pointers in data are not position independent." > This causes data pointer to become invalid if >

[PATCH v5] Avoid crash calling PrintErrMesg from efi_multiboot2

2025-01-22 Thread Frediano Ziglio
Although code is compiled with -fpic option data is not position independent. This causes data pointer to become invalid if code is not relocated properly which is what happens for efi_multiboot2 which is called by multiboot entry code. Code tested adding PrintErrMesg(L"Test message", EFI_BUFFE