feat: rework deadlock handling #1
Merged
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
The current practice of filtering specific access masks out that can cause deadlocks in NtQueryObject also causes other handles, e.g. most named pipes, to be ignored. To improve on this, use a native thread instead that can be killed in case of a deadlock. Our "main" go routine can communicate with the go function running on the native thread via a pair of pipes.
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.
The current practice of filtering specific access masks out that
can cause deadlocks in NtQueryObject also causes other handles,
e.g. most named pipes, to be ignored.
To improve on this, use a native thread instead that can be killed
in case of a deadlock. Our "main" go routine can communicate with
the go function running on the native thread via a pair of pipes.