Bug 1889892
| Summary: | glibc: pthread_cond_wait missed wakeup (swbz#25847) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michael Bacarella <michael.bacarella> | ||||||||
| Component: | glibc | Assignee: | Frédéric Bérat <fberat> | ||||||||
| Status: | ASSIGNED --- | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 42 | CC: | aoliva, ashankar, codonell, dj, edwin+bugs, fweimer, law, mfabian, pfrankli, rth, schwerin, sipoyare | ||||||||
| Target Milestone: | --- | Keywords: | Bugfix, Reopened | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | glibc-2.40.9000-30.fc42, glibc-2.40-22.fc41 | Doc Type: | If docs needed, set a value | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | |||||||||||
| : | 1979990 (view as bug list) | Environment: | |||||||||
| Last Closed: | 2025-03-13 01:10:56 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 1979990 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Michael Bacarella
2020-10-20 20:30:15 UTC
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. |