| Message ID | 1485877949-21981-1-git-send-email-ard.biesheuvel@linaro.org |
|---|---|
| State | Superseded |
| Headers | show |
On Tue, Jan 31, 2017 at 4:52 PM, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote: > The ARM decompressor is finicky when it comes to uninitialized variables > with local linkage, the reason being that it may relocate .text and .bss > independently when executing from ROM. This is only possible if all > references into .bss from .text are absolute, and this happens to be the > case for references emitted under -fpic to symbols with external linkage, > and so all .bss references must involve symbols with external linkage. > > When building the ARM stub using clang, the initialized local variable > __chunk_size is optimized into a zero-initialized flag that indicates > whether chunking is in effect or not. This flag is therefore emitted into > .bss, which triggers the ARM decompressor's diagnostics, resulting in a > failed build. > > Under UEFI, we never execute the decompressor from ROM, so the diagnostic > makes little sense here. But we can easily work around the issue by making > __chunk_size global instead. > > However, given that the file I/O chunking that is controlled by the > __chunk_size variable is intended to work around known bugs on various > x86 implementations of UEFI, we can simply make the chunking an x86 > specific feature. This is an improvement by itself, and also removes the > need to parse the efi= options in the stub entirely. > > Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org> Tested-by: Arnd Bergmann <arnd@arndb.de -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, 31 Jan, at 03:52:29PM, Ard Biesheuvel wrote: > The ARM decompressor is finicky when it comes to uninitialized variables > with local linkage, the reason being that it may relocate .text and .bss > independently when executing from ROM. This is only possible if all > references into .bss from .text are absolute, and this happens to be the > case for references emitted under -fpic to symbols with external linkage, > and so all .bss references must involve symbols with external linkage. > > When building the ARM stub using clang, the initialized local variable > __chunk_size is optimized into a zero-initialized flag that indicates > whether chunking is in effect or not. This flag is therefore emitted into > .bss, which triggers the ARM decompressor's diagnostics, resulting in a > failed build. > > Under UEFI, we never execute the decompressor from ROM, so the diagnostic > makes little sense here. But we can easily work around the issue by making > __chunk_size global instead. > > However, given that the file I/O chunking that is controlled by the > __chunk_size variable is intended to work around known bugs on various > x86 implementations of UEFI, we can simply make the chunking an x86 > specific feature. This is an improvement by itself, and also removes the > need to parse the efi= options in the stub entirely. > > Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org> > --- > drivers/firmware/efi/libstub/efi-stub-helper.c | 12 +++++++++++- > 1 file changed, 11 insertions(+), 1 deletion(-) Reviewed-by: Matt Fleming <matt@codeblueprint.co.uk> -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/drivers/firmware/efi/libstub/efi-stub-helper.c b/drivers/firmware/efi/libstub/efi-stub-helper.c index 757badc1debb..5a418a6a33bf 100644 --- a/drivers/firmware/efi/libstub/efi-stub-helper.c +++ b/drivers/firmware/efi/libstub/efi-stub-helper.c @@ -351,6 +351,14 @@ efi_status_t efi_parse_options(char *cmdline) char *str; /* + * Currently, the only efi= option we look for is 'nochunk', which + * is intended to work around known issues on certain x86 UEFI + * versions. So ignore for now on other architectures. + */ + if (!IS_ENABLED(CONFIG_X86)) + return EFI_SUCCESS; + + /* * If no EFI parameters were specified on the cmdline we've got * nothing to do. */ @@ -523,7 +531,9 @@ efi_status_t handle_cmdline_files(efi_system_table_t *sys_table_arg, size = files[j].size; while (size) { unsigned long chunksize; - if (size > __chunk_size) + + if (IS_ENABLED(CONFIG_X86) && + size > __chunk_size) chunksize = __chunk_size; else chunksize = size;
The ARM decompressor is finicky when it comes to uninitialized variables with local linkage, the reason being that it may relocate .text and .bss independently when executing from ROM. This is only possible if all references into .bss from .text are absolute, and this happens to be the case for references emitted under -fpic to symbols with external linkage, and so all .bss references must involve symbols with external linkage. When building the ARM stub using clang, the initialized local variable __chunk_size is optimized into a zero-initialized flag that indicates whether chunking is in effect or not. This flag is therefore emitted into .bss, which triggers the ARM decompressor's diagnostics, resulting in a failed build. Under UEFI, we never execute the decompressor from ROM, so the diagnostic makes little sense here. But we can easily work around the issue by making __chunk_size global instead. However, given that the file I/O chunking that is controlled by the __chunk_size variable is intended to work around known bugs on various x86 implementations of UEFI, we can simply make the chunking an x86 specific feature. This is an improvement by itself, and also removes the need to parse the efi= options in the stub entirely. Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org> --- drivers/firmware/efi/libstub/efi-stub-helper.c | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) -- 2.7.4 -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html