public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/16133] Access to __thread variable may call malloc
Date: Wed, 05 Feb 2014 03:32:00 -0000	[thread overview]
Message-ID: <bug-16133-131-qkuijU84wl@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16133-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=16133

--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".

The branch, allan/revert-TLS-changes has been created
        at  063f2598738c340558462923d2b17a665713ed2e (commit)

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=063f2598738c340558462923d2b17a665713ed2e

commit 063f2598738c340558462923d2b17a665713ed2e
Author: Allan McRae <allan@archlinux.org>
Date:   Wed Feb 5 12:51:40 2014 +1000

    Revert "BZ 16133 has been fixed (async signal safe TLS)."

    This reverts commit a494421f5268df333c589d71104a39bb6a9cff19.

    Conflicts:
        NEWS

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=c364820b18326c354ce371daff340b97da3d03db

commit c364820b18326c354ce371daff340b97da3d03db
Author: Allan McRae <allan@archlinux.org>
Date:   Wed Feb 5 12:20:11 2014 +1000

    Revert "Patch [1/4] async-signal safe TLS."

    This reverts commit 69a17d9d245dc3551792e95e1823cc2d877592f3.

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=c1543ec02e4dbbb39a7c452f72aa82a933f5232a

commit c1543ec02e4dbbb39a7c452f72aa82a933f5232a
Author: Allan McRae <allan@archlinux.org>
Date:   Wed Feb 5 12:19:56 2014 +1000

    Revert "Patch 3/4 of the effort to make TLS access async-signal-safe."

    This reverts commit 35e8f7ab94c910659de9d507aa0f3e1f8973d914.

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=40cd533ceca15faddd466a7fdd1831d8a1bfbce6

commit 40cd533ceca15faddd466a7fdd1831d8a1bfbce6
Author: Allan McRae <allan@archlinux.org>
Date:   Wed Feb 5 12:19:19 2014 +1000

    Revert "Patch 2/4 of the effort to make TLS access async-signal-safe."

    This reverts commit 1f33d36a8a9e78c81bed59b47f260723f56bb7e6.

    Conflicts:
        elf/dl-misc.c

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=9ca53ad185c8e50d0488ef0a419930e48b14f182

commit 9ca53ad185c8e50d0488ef0a419930e48b14f182
Author: Allan McRae <allan@archlinux.org>
Date:   Wed Feb 5 12:17:23 2014 +1000

    Revert "Async-signal safe TLS."

    This reverts commit 7f507ee17aee720fa423fa38502bc3caa0dd03d7.

    Conflicts:
        ChangeLog
        nptl/tst-tls7.c
        nptl/tst-tls7mod.c

-----------------------------------------------------------------------

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-02-05  3:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07  0:52 [Bug dynamic-link/16133] New: " ppluzhnikov at google dot com
2013-11-23 23:42 ` [Bug dynamic-link/16133] " carlos at redhat dot com
2014-01-12  0:57 ` ppluzhnikov at google dot com
2014-01-12  1:00 ` cvs-commit at gcc dot gnu.org
2014-02-05  3:32 ` cvs-commit at gcc dot gnu.org [this message]
2014-02-05 11:24 ` cvs-commit at gcc dot gnu.org
2014-02-05 11:24 ` cvs-commit at gcc dot gnu.org
2014-02-05 14:46 ` ppluzhnikov at google dot com
2014-02-05 14:46 ` ppluzhnikov at google dot com
2014-02-05 22:47 ` cvs-commit at gcc dot gnu.org
2014-02-05 22:47 ` cvs-commit at gcc dot gnu.org
2014-06-13  9:34 ` fweimer at redhat 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-16133-131-qkuijU84wl@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).