unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] NEWS: Deprecate weak libpthread symbols for single-threaded checks
Date: Fri, 24 Jul 2020 16:40:04 -0400	[thread overview]
Message-ID: <1bc15e73-3d9f-8f63-eccc-952ed8bab27b@redhat.com> (raw)
In-Reply-To: <875zad7yrc.fsf@oldenburg2.str.redhat.com>

On 7/24/20 10:50 AM, 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
> 

OK for 2.32.

Reviewed-by: Carlos O'Donell <carlos@redhat.com>

-- 
Cheers,
Carlos.


      parent reply	other threads:[~2020-07-24 20:40 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
2020-07-24 20:40   ` Carlos O'Donell via Libc-alpha
2020-07-24 20:40 ` Carlos O'Donell via Libc-alpha [this message]

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=1bc15e73-3d9f-8f63-eccc-952ed8bab27b@redhat.com \
    --to=libc-alpha@sourceware.org \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    /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).