Potential lock inversion problem in transport::tcp::Context::signalFailure

Question

Potential lock inversion problem in transport::tcp::Context::signalFailure

Closed this issue 5 years ago · 2 comments

It takes the context mutex and then iterates over the pairs. If the device thread is processing events and calls into a recv-from-any path we reach deadlock. Can happen only during error handling.

Answer 1 · 2019-01-30T00:49:21.000Z

Reported by @jgehring.

Answer 2 · 2019-11-06T10:59:21.000Z

This is addressed in #211.