[codex] Fix IAR file lock mutex bounds#567
Draft
Old-Ding wants to merge 1 commit into
Draft
Conversation
29ba95c to
e4fdfdf
Compare
Signed-off-by: Old-Ding <35417409+Old-Ding@users.noreply.github.com>
e4fdfdf to
d24bb49
Compare
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
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.
Summary
_MAX_FLOCK_MAX_LOCKRoot cause
The file lock mutex pool is sized with
_MAX_FLOCK, but its round-robin allocation checks used_MAX_LOCKin two places. When_MAX_FLOCKis larger than_MAX_LOCK, the allocator can wrap or report exhaustion using the system-lock limit instead of the file-lock pool size.Validation
git diff --check_MAX_LOCKto_MAX_FLOCKfile_lockreferences use_MAX_LOCK