[SRU] pthread_rwlock_trywrlock results in hang
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
glibc (Debian) |
Fix Released
|
Unknown
|
|||
glibc (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Balint Reczey |
Bug Description
[Impact]
* pthread_
* We are especially able to reproduce the problem with BIND 9.16.x when --with-
* But the impact is not limited to BIND 9.16, but any multithreaded application using phtread rwlocks
[Test Case]
* Fetch the source program and build it:
$ sudo apt install build-essential -y
$ wget https:/
$ gcc bug23844.wr.c -lpthread -o bug23844wr
* Run the resulting binary a few times. On affected systems, it should hang in less then 10 attempts.
$ ./bug23844rw
trylock_wr
500000
(...)
$ ./bug23844.wr
trylock_wr
<hangs>
[Regression Potential]
* The upstream fix has been in glibc 2.30 and later
* Debian has the fix in 2.28-8 as part of "git-updates.diff" from February 2019
Related branches
- Dimitri John Ledkov (community): Approve
- Canonical Server Core Reviewers: Pending requested
- Canonical Server: Pending requested
- Adam Conrad: Pending requested
- git-ubuntu developers: Pending requested
-
Diff: 702 lines (+677/-0)3 files modifieddebian/changelog (+7/-0)
debian/patches/all/branch-pthread_rwlock_trywrlock-hang-23844.patch (+669/-0)
debian/patches/series (+1/-0)
CVE References
description: | updated |
Changed in glibc (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in glibc (Ubuntu Bionic): | |
status: | New → Triaged |
Changed in glibc (Ubuntu): | |
status: | Triaged → Fix Released |
Changed in glibc (Debian): | |
status: | Unknown → Fix Released |
description: | updated |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1864864/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]