-
Notifications
You must be signed in to change notification settings - Fork 8.2k
llext: load: memcpy section header #97993
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wow, interesting. Is this compiler-specific? IIRC I've seen a structure assignment being replaced by the compiler with a memcpy builtin. That implementation shouldn't assume any alignment. And in general - as long as there's no alignment attribute, is it valid to assume any such alignment? I think structures are defined to be aligned in arrays, but stand-alone - I wasn't aware of such restrictions at least
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We've ran into similar issues with mipi sys-t logging in the past which, yes, when derefencing arbitrary pointers and applying assignment would result in unaligned access faults just like this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@teburd but that depends on the type of the pointer. If it's a
char *certainly no alignment is needed. For a 2-byte type a two-byte alignment is needed and so on. And for a structure? Even the fact that the linker placed a section header above without a 4-byte alignment suggests, that it's valid. And then the compiler fails to generate code to read it. Interesting.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Its not clear to me why the section header should have any alignment requirements, its a binary data structure, not executable code. Even if it did have an alignment, what should that be? A
uint32_talignment, that would work fine for the 32 bit targets, would still have an incorrect alignment on 64 bit platforms.