There is a slight chance that the code will race and close the epoll descriptor when another thread has already grabbed the socket and initialized it.
This seem to cause threads to get stuck waiting forever.
Not confirmed but the most likely working hypothesis in a bug related to rpc.gssd which now makes heavy use of threads.
There is a slight chance that the code will race and close the epoll descriptor when another thread has already grabbed the socket and initialized it.
This seem to cause threads to get stuck waiting forever.
Not confirmed but the most likely working hypothesis in a bug related to rpc.gssd which now makes heavy use of threads.