truncate backing file path exceeding 64 bytes in LoopInfo #411
Conversation
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
lujinda
force-pushed
the
loopfile_length_greater_64
branch
from
6f94ace to
db9eb44
Compare
When the backing file path exceeds 64 bytes, an 'out of range' error occurs due to the limitation of the `file_name` field in `LoopInfo`. This commit truncates the file path to ensure it does not exceed the maximum supported length, preventing the error while maintaining usability. Signed-off-by: jinda.ljd <[email protected]>
lujinda
force-pushed
the
loopfile_length_greater_64
branch
from
db9eb44 to
eb01057
Compare
mxpv
approved these changes
Jul 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When the backing file path exceeds 64 bytes, an 'out of range' error occurs due to the limitation of the
file_namefield inLoopInfo. This commit truncates the file path to ensure it does not exceed the maximum supported length, preventing the error while maintaining usability.