fix deadlock in shmget #9
Merged
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.
shmgetdeadlocks when called more than once in the same process. It locks the mutex, then callsashv_read_remote_segment, which asks the background thread in the same process to find a shmid, which in turn tries to lock the mutex which is already locked. I included a simple trivial test case that hits the deadlock.I actually found this in Postgres, noticing that a
CREATE TABLE AS ...query was never returning, and the process that was executing the query was stuck doing nothing. strace showed one thread stuck reading from a socket, and another stuck waiting on a lock.