Bug 1622669 - glibc: Fix waiters-after-spinning case in pthread_cond_broadcast
Summary: glibc: Fix waiters-after-spinning case in pthread_cond_broadcast
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: 27
Hardware: All
OS: Linux
high
medium
Target Milestone: ---
Assignee: Florian Weimer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1622675
TreeView+ depends on / blocked
 
Reported: 2018-08-27 17:28 UTC by Florian Weimer
Modified: 2018-11-30 22:32 UTC (History)
11 users (show)

Fixed In Version: glibc-2.28.9000-2.fc30 glibc-2.28-8.fc29 glibc-2.27-32.fc28 glibc-2.26-30.fc27
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1622675 (view as bug list)
Environment:
Last Closed: 2018-11-30 22:32:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Sourceware 23538 0 P2 RESOLVED Hang in pthread_cond_broadcast 2020-12-23 18:53:49 UTC

Description Florian Weimer 2018-08-27 17:28:28 UTC
We need to backport this upstream commit all the way back to Fedora 27:

commit 99ea93ca31795469d2a1f1570f17a5c39c2eb7e2
Author: Martin Kuchta <martin.kuchta>
Date:   Mon Aug 27 17:03:35 2018 +0200

    pthread_cond_broadcast: Fix waiters-after-spinning case [BZ #23538]

(Fedora 26 would be affected as well, but is out of support.)

Comment 1 Fedora Update System 2018-08-29 11:58:53 UTC
glibc-2.28-8.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-7baa4e2d9d

Comment 2 Fedora Update System 2018-08-29 12:09:47 UTC
glibc-2.27-32.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-fb2271134d

Comment 3 Fedora Update System 2018-08-29 12:55:09 UTC
glibc-2.26-30.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-c1ef35a4f9

Comment 4 Fedora Update System 2018-08-29 19:07:44 UTC
glibc-2.28-8.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-7baa4e2d9d

Comment 5 Fedora Update System 2018-08-29 23:14:28 UTC
glibc-2.28-9.fc29 has been pushed to the Fedora 29 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-2018-7baa4e2d9d

Comment 6 Fedora Update System 2018-08-30 04:23:34 UTC
glibc-2.26-30.fc27 has been pushed to the Fedora 27 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-2018-c1ef35a4f9

Comment 7 Fedora Update System 2018-08-30 05:55:12 UTC
glibc-2.27-32.fc28 has been pushed to the Fedora 28 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-2018-fb2271134d

Comment 8 Fedora Update System 2018-09-02 05:56:10 UTC
glibc-2.27-32.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.

Comment 9 The Source 2018-09-03 04:43:33 UTC
glibc-headers.i686 is missing from x86_64 f28 repository for this update, I can't  install glibc-devel.i686 because of this.

Comment 10 Florian Weimer 2018-09-03 06:19:36 UTC
(In reply to The Source from comment #9)
> glibc-headers.i686 is missing from x86_64 f28 repository for this update, I
> can't  install glibc-devel.i686 because of this.

This is a known issue with the updates-testing compose: https://pagure.io/releng/issue/7071

Comment 11 Fedora Update System 2018-09-07 15:24:19 UTC
glibc-2.26-30.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2018-09-21 05:22:49 UTC
glibc-2.28-9.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.

Comment 13 Ben Cotton 2018-11-27 14:38:38 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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.

Comment 14 Ben Cotton 2018-11-30 22:32:41 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.