From: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH] NEWS: Deprecate weak libpthread symbols for single-threaded checks
Date: Fri, 24 Jul 2020 13:36:57 -0300 [thread overview]
Message-ID: <b8f5a29c-42af-cfc4-725c-6d2b8df89dc1@linaro.org> (raw)
In-Reply-To: <875zad7yrc.fsf@oldenburg2.str.redhat.com>
On 24/07/2020 11:50, Florian Weimer via Libc-alpha wrote:
> Recommend the new __libc_single_thread variable instead.
>
> ---
> NEWS | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/NEWS b/NEWS
> index 83aed60e19..7fb167e650 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -134,6 +134,14 @@ Deprecated and removed features, and other changes affecting compatibility:
> or contents might be overwritten on subsequent calls in the same thread or
> if the thread is terminated. It makes strerror MT-safe.
>
> +* Using weak references to libpthread functions such as pthread_create
> + or pthread_key_create to detect the singled-threaded nature of a
> + program is an obsolescent feature. Future versions of glibc will
> + define pthread_create within libc.so.6 itself, so such checks will
> + always flag the program as multi-threaded. Applications should check
> + the __libc_single_threaded variable declared in
> + <sys/single_threaded.h> instead.
> +
> * The "files" NSS module no longer supports the "key" database (used for
> secure RPC). The contents of the /etc/publickey file will be ignored,
> regardless of the settings in /etc/nsswitch.conf. (This method of
>
Should we add it on the 'Major features' instead along with the single-threaded
entry?
next prev parent reply other threads:[~2020-07-24 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 14:50 [PATCH] NEWS: Deprecate weak libpthread symbols for single-threaded checks Florian Weimer via Libc-alpha
2020-07-24 16:36 ` Adhemerval Zanella via Libc-alpha [this message]
2020-07-24 20:40 ` Carlos O'Donell via Libc-alpha
2020-07-24 20:40 ` Carlos O'Donell via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b8f5a29c-42af-cfc4-725c-6d2b8df89dc1@linaro.org \
--to=libc-alpha@sourceware.org \
--cc=adhemerval.zanella@linaro.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).