Bug#952609: marked as done (libc6: pthread_rwlock_trywrlock hangs)
Your message dated Wed, 26 Feb 2020 23:44:31 +0100
with message-id <8642CC10-4785-48BA-ABB3-64373C767354@sury.org>
and subject line Re: Bug#952609: libc6: pthread_rwlock_trywrlock hangs
has caused the Debian Bug report #952609,
regarding libc6: pthread_rwlock_trywrlock hangs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
952609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952609
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.28-10
Severity: important
Tags: upstream patch
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Dear Maintainer,
glibc after 2.26 (included) and before 2.30 hangs in pthread_rwlock_tryrwlock
and pthread_rwlock_tryrdlock, the details and test cases can be found in
https://sourceware.org/bugzilla/show_bug.cgi?id=23844#c14
This especially hits BIND 9.16 when using pthread_rwlock (instead of custom ISC
rwlock).
So, could you please fix this in buster? For sid, this will get fixed as part
of regular updated to 2.30,
The patch is quite small and the impact of pthread_rwlock_try(rw|rd)lock()
hanging is pretty severe. Also quite hard to find - we spent couple of days
hunting the bug in BIND 9 and it turned to be problem in glibc.
Thanks,
Ondrej
- -- System Information:
Debian Release: 10.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-8-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-----BEGIN PGP SIGNATURE-----
iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAl5Wl6hfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcICsA//W4g/fPvaxg3h41PzZoEw6f5/Wc82KI8WHczUFQWQRnK+MVgrSjOhkI0E
w6sZfAfE4fOJmZWh0ZNp9tXlaf05qFq86HBswJmrWLnSSd0LHB/PI59i+42dikQT
Z3MquY1F6ouC4lzA5NrsPdaAof2qXcSRrua3e3SOAiIN9HO43XOZxhvE8uqFZJA4
ZswgXLnWcWZLkTfdiASzQ+Dp2oAo6OJFHTdgRveOnNAbmQAFB1ANLe/echpSE2PJ
hrVD9RJwuL4/bLWYr9LwWdUM9IvZhh+QwjrSm52jcF40b9yHOcRnvZ8LZuWnf7gm
CuB+ekJY0N6vDz1nFy4c8b6/vrK+grsfXFZyiwItD3sfE5rJORjeTT3VosmPyiSy
LqAXfpiPKPlXGZhIe5ipxCJQ7k092brTjoxBmHuIpwDHE4u5FXqndRgh+qXKJYdQ
WAnG2RrvZ6VWLpCUnYq1gC+f2B+0MB7rAfX8jSRoxRGKmI/ubyc7Z3vdBwxYeqo4
eQ0XqgnppUsqkTWDJpYB1KSuGfhCVmVR8gJ7oE/4qXkEOccHyzYo+u0ZYJ8KMS4v
doLjWojTfd+NWRpN2b4+J8Vz2MBU0IdWVkuu17VbgQ04I/Qf3Ww7EEl1CITTrjUx
jI0VrKo/nQj8+CkrA56B2hgynqhvni5ehs7uJ7IhAl6KRO10cF8=
=z3LE
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Control: fixed -1 glibc/2.28-8
Control: notfound -1 glibc/2.28-10
Control: found -1 glibc/2.27-1
Thanks Aurelien, so it’s actually only Ubuntu Bionic that’s being affected
by the bug.
Ondrej
--
Ondřej Surý
ondrej@sury.org
> On 26 Feb 2020, at 23:29, Aurelien Jarno <aurelien@aurel32.net> wrote:
>
> On 2020-02-26 17:07, Ondřej Surý wrote:
>> Package: libc6
>> Version: 2.28-10
>> Severity: important
>> Tags: upstream patch
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA512
>>
>> Dear Maintainer,
>>
>> glibc after 2.26 (included) and before 2.30 hangs in pthread_rwlock_tryrwlock
>> and pthread_rwlock_tryrdlock, the details and test cases can be found in
>> https://sourceware.org/bugzilla/show_bug.cgi?id=23844#c14
>>
>> This especially hits BIND 9.16 when using pthread_rwlock (instead of custom ISC
>> rwlock).
>>
>> So, could you please fix this in buster? For sid, this will get fixed as part
>> of regular updated to 2.30,
>
> This patch is already included since glibc 2.28-8 as part of pulling the
> upstream stable branch. So it should already be fixed in buster, bullseye
> and sid.
>
> At least I confirm that the bug23844.wr.c testcase from the upstream bug
> report sometimes fail with glibc 2.28-7, but never fails with glibc
> 2.28-8.
>
> Regards,
> Aurelien
>
> --
> Aurelien Jarno GPG: 4096R/1DDD8C9B
> aurelien@aurel32.net http://www.aurel32.net
--- End Message ---
Reply to: