On Mon, Nov 14, 2016 at 12:19:06PM +0100, Lukas Wunner wrote: > On Sat, Nov 12, 2016 at 08:55:14PM +0000, Matt Fleming wrote: > > On Mon, 07 Nov, at 12:17:00PM, Lukas Wunner wrote: > > > Another oddity is that info_sz is declared u32 in __file_size32(), > > > yet the spec says that the third argument to EFI_FILE_PROTOCOL.GetInfo() > > > is of type UINTN, which I assume is 64 bit regardless of mixed-mode, > > > or am I missing something? Patch [1/2] uses an unsigned long instead. > > > > UINTN is an unsigned value of native width as seen by the firmware. On > > 32-bit firmware that's 32-bits and 64-bit firmware 64-bits. > > > > Using 'u32' in __file_size32() is correct, unsigned long is not. > > Okay since this is all little endian, it should be okay to have a > 64 bit wide variable on the stack whose address is passed to GetInfo() > as BufferSize argument. But I guess I need to initialize it to 0 > upon declaration so that the upper 32 bit are zeroed out in mixed mode, > right? That would be a bug in patch [1/2] then. Oh the info_sz variable *is* already initialized to 0 before the first invocation of GetInfo(). So the patch should be fine, reviewed it once more with the explanations in mind that you provided and couldn't see anything else that would cause issues in mixed-mode. Thanks, Lukas -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
