Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

library_manager: llext: don't try to copy .bss #9846

Merged
merged 1 commit into from
Feb 20, 2025

Conversation

lyakh
Copy link
Collaborator

@lyakh lyakh commented Feb 19, 2025

When copying LLEXT modules from DRAM to SRAM we allocate and copy .data and .bss together because they have the same access flags, but .bss doesn't have to be copied, this can in fact generate an error because it isn't present in the ELF image. Only copy valid sections.

When copying LLEXT modules from DRAM to SRAM we allocate and copy
.data and .bss together because they have the same access flags, but
.bss doesn't have to be copied, this can in fact generate an error
because it isn't present in the ELF image. Only copy valid sections.

Reported-by: Tomasz Leman <[email protected]>
Signed-off-by: Guennadi Liakhovetski <[email protected]>
@lyakh
Copy link
Collaborator Author

lyakh commented Feb 20, 2025

@lgirdwood lgirdwood merged commit 1d1b1dd into thesofproject:main Feb 20, 2025
44 of 49 checks passed
@lyakh lyakh deleted the bss branch February 21, 2025 07:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants