public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/1890] strerror() unnecessarily non thread-safe
Date: Thu, 15 Jun 2023 09:48:14 +0000 [thread overview]
Message-ID: <bug-1890-131-5Sn3v2aWcY@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-1890-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=1890
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |2.32
Resolution|--- |FIXED
Status|ASSIGNED |RESOLVED
Assignee|fweimer at redhat dot com |unassigned at sourceware dot org
--- Comment #8 from Florian Weimer <fweimer at redhat dot com> ---
Fixed for 2.32 via:
commit 28aff047818eb1726394296d27b9c7885340bead
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date: Thu May 14 17:44:15 2020 -0300
string: Implement strerror in terms of strerror_l
If the thread is terminated then __libc_thread_freeres will free the
storage via __glibc_tls_internal_free.
It is only within the calling thread that this matters. It makes
strerror MT-safe.
Checked on x86-64-linux-gnu, i686-linux-gnu, powerpc64le-linux-gnu,
and s390x-linux-gnu.
Tested-by: Carlos O'Donell <carlos@redhat.com>
Reviewed-by: Carlos O'Donell <carlos@redhat.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-06-15 9:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-1890-131@http.sourceware.org/bugzilla/>
2020-12-21 2:43 ` jscott at posteo dot net
2023-06-15 9:48 ` fweimer at redhat dot com [this message]
2023-06-15 9:50 ` fweimer at redhat dot com
2023-10-26 23:20 ` gabravier at gmail dot com
2023-11-01 1:59 ` bruno at clisp dot org
2023-12-12 11:40 ` fweimer at redhat dot com
2023-12-12 12:21 ` bruno at clisp dot org
2023-12-13 9:39 ` fweimer at redhat dot com
2005-11-19 15:15 [Bug libc/1890] New: " stefan dot puiu at gmail dot com
2005-11-22 18:13 ` [Bug libc/1890] " drepper at redhat dot com
2005-11-23 7:35 ` stefan dot puiu at gmail dot com
2005-11-23 8:31 ` drepper at redhat dot com
2005-11-23 9:15 ` stefan dot puiu at gmail dot com
2005-11-23 9:26 ` stefan dot puiu at gmail dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-1890-131-5Sn3v2aWcY@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).