ntdll: Don't leak objattr allocation in NtCreateSemaphore. #219
Conversation
This file contains 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
fsync/esync_create_semaphore allocates objattr on their own, and objattr allocated in NtCreateSemaphore was getting leaked. Like NtCreateEvent, move the objattr allocation after fsync/esync early return to avoid double allocation.
|
Thanks! Pushed to Experimental branch. |
Plagman
pushed a commit
that referenced
this pull request
Feb 20, 2024
Plagman
pushed a commit
that referenced
this pull request
Feb 26, 2024
Plagman
pushed a commit
that referenced
this pull request
May 3, 2024
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.
fsync/esync_create_semaphore allocates objattr on their own, and objattr allocated in NtCreateSemaphore was getting leaked.
Like NtCreateEvent, move the objattr allocation after fsync/esync early return to avoid double allocation.