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.
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
littlefs: make block size configurable at compile time #18141
littlefs: make block size configurable at compile time #18141
Changes from all commits
41c0b1e
a29d5c2
4dd5cb3
578e628
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I made this a
uint16_t
because I chose the maximum ofCONFIG_LITTLEFS2_MIN_BLOCK_SIZE_EXP
to be 2^15 in Kconfig.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.
This addition resulted in the subsequent buffers no longer being aligned two 4 bytes by accident, which triggered unaligned memory accesses. On Cortex M0+, such as used by the
samr21-xpro
, this then resulted in hard faults.But the issue really is that alignment requirements need to be communicated to the compiler. It was just luck that this worked before.
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.
Well not so much luck since the
uint32_t
will always be word-aligned.Moving
sectors_per_block
to end end of the struct should be the simple fix. (The buffers are already word-multiples)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.
I doubt anyone placed them after a
uint32_t
member to align them without adding a comment to warn about breakage. To me, this looks like we got lucky here :)(E.g.
iolist_t
andpkt_snip_t
have a common memory layout, but that is documented to avoid anyone from breaking it. I would expect similar comments here if that was inentionally.)