Description of problem: This bug was submitted by Qin Li to glibc bugzilla earlier this year, with a one-line patch, though it hasn't been merged into glibc yet: https://sourceware.org/bugzilla/show_bug.cgi?id=25847 Version-Release number of selected component: glibc-2.27 onwards How reproducible: reliably, try the repro from the sourceware url above Actual results: deadlocks after 30-120 minutes on a 4-core Fedora 32 box Expected results: should never deadlock Additional info: This bug in pthread conditions will deadlock the OCaml runtime, as well as Python and .NET applications. The bug was introduced in glibc 2.27 and is still present in glibc 2.31. I confirm the repro from the above deadlocks on Fedora 32. Takes about 30-180 minutes on a 4 core server. I further confirm that the one-line fix to glibc at the above applies cleanly to Fedora 32's glibc source rpm, and does not deadlock after running the repro for more than 30 hours. Please kindly consider merging the one-line fix into Fedora glibc. More background about this bug, for the sake of future internet searchers: * https://discuss.ocaml.org/t/is-there-a-known-recent-linux-locking-bug-that-affects-the-ocaml-runtime
Created attachment 1722977 [details] test case repro from sourceware entry will deadlock
Created attachment 1722978 [details] one-line patch to glibc that fixes the deadlock
We are looking to fix this for Fedora and Red Hat Enterprise Linux 8 as this has impact to users on both platforms.
Created attachment 1725573 [details] testcase with abort() on stuck Small modification to upstream testcase that abort()s when the loop is stuck for several iterations.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Still a bug, and still in Rawhide.
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35.
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.
This is fixed in Fedora Rawhide (f43), and in Fedora 42 (f42), but not yet in f41 or f40.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle. Changing version to 42.
Fedora 40 and Fedora 41 still need this fix.
Fedora 41 scratch build with the fix: https://koji.fedoraproject.org/koji/taskinfo?taskID=129956568 We can take this upstream to get a backport into glibc 2.40 and glibc 2.39, but upstream has to agree it would consider the upgrade scenario acceptable. Until that point the next step is a backport into F41, and F40.
FEDORA-2025-85313b82b2 (glibc-2.40-22.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-85313b82b2
FEDORA-2025-85313b82b2 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-85313b82b2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-85313b82b2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-85313b82b2 (glibc-2.40-22.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-0a780eb540 (glibc-2.40-23.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-0a780eb540
Fedora 40 still needs to be fixed.
FEDORA-2025-0a780eb540 (glibc-2.40-23.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
Upstream release/2.40/master, and release/2.39/master are now fixed. This issue can be resolved by syncing from release/2.39/master to F40.