Description of problem: Glibc 2.25 has a bug in pthread_mutex_lock which may lead to deadlock. This is alredy fixed upstream, see https://sourceware.org/bugzilla/show_bug.cgi?id=21778 Version-Release number of selected component (if applicable): glibc 2.25 How reproducible: 100 % Steps to Reproduce: 1. install Knot Resolver (knot-resolver) 2. run the resolver with multiple processes sharing single cache (kresd parameter -f 2) 3. put the resolver under heavy load (e.g. using resperf tool) Actual results: Resolver deadlocks within a minute or two. Expected results: It should not deadlock. Additional info: We have verified that the problem does not appear on Glibc 2.26. GDB shows deadlock on the right spot pointing towards https://sourceware.org/bugzilla/show_bug.cgi?id=21778 .
I'm going to backport the upstream fixes into the upstream stable branch and import that into Fedora.
Awesome, thank you!
Bodhi update: https://bodhi.fedoraproject.org/updates/FEDORA-2017-103e80de0b (Somehow, it didn't make it to the bug so far.)
glibc-2.25-10.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-103e80de0b
glibc-2.25-10.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.