Fix #983: Use OS_MAX_FILE_NAME instead of OS_MAX_PATH_LEN in CFE_FS_ExtractFilenameFromPath#984
Open
linerfan5114 wants to merge 1 commit into
Open
Conversation
…FS_ExtractFilenameFromPath
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #983
CFE_FS_ExtractFilenameFromPath() validates the extracted filename length against OS_MAX_PATH_LEN, but it should use OS_MAX_FILE_NAME since it only extracts the file name portion, not the full path. This inconsistency with OSAL parameter definitions can cause validation errors when a user defines a variable using OS_MAX_FILE_NAME.