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 11:24:00 -0000 [thread overview]
Message-ID: <bug-16133-131-n034CSSt38@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 #5 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 b3ece0e0a4912bfedd6da72f2ae1cf5d1b10731b (commit)
- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=b3ece0e0a4912bfedd6da72f2ae1cf5d1b10731b
commit b3ece0e0a4912bfedd6da72f2ae1cf5d1b10731b
Author: Allan McRae <allan@archlinux.org>
Date: Wed Feb 5 21:22:19 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=59cf6f94f13991336bd958a4491ee9d57109a7bd
commit 59cf6f94f13991336bd958a4491ee9d57109a7bd
Author: Allan McRae <allan@archlinux.org>
Date: Wed Feb 5 21:21:09 2014 +1000
Revert "Patch [1/4] async-signal safe TLS."
This reverts commit 69a17d9d245dc3551792e95e1823cc2d877592f3.
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=097c7e230df0e16bf950456676a48281e9f3a905
commit 097c7e230df0e16bf950456676a48281e9f3a905
Author: Allan McRae <allan@archlinux.org>
Date: Wed Feb 5 21:21:00 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=ddd7cff1fc7ca773ee02981f5c2f80116a32b325
commit ddd7cff1fc7ca773ee02981f5c2f80116a32b325
Author: Allan McRae <allan@archlinux.org>
Date: Wed Feb 5 21:19:51 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
Also reverts the follow commits that were bug fixes to new code introduced
in the above commit:
063b2acbce83549df82ab30f5af573f1b9c4bd19
b627fdd58554bc36bd344dc40a8787c4b7a9cc46
e81c64bba13d2d8b2a4e53254a82cc80f27c8497
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=57f6ca1e5d4d50961e904a986b86174614316653
commit 57f6ca1e5d4d50961e904a986b86174614316653
Author: Allan McRae <allan@archlinux.org>
Date: Wed Feb 5 21:14:59 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.
next prev parent reply other threads:[~2014-02-05 11:24 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
2014-02-05 11:24 ` cvs-commit at gcc dot gnu.org [this message]
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-n034CSSt38@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).