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/16634] Application calling dlopen("./a.out",...) may run into  _dl_allocate_tls_init: Assertion `listp != ((void *)0)' failed!
Date: Mon, 24 Mar 2014 18:14:00 -0000	[thread overview]
Message-ID: <bug-16634-131-8bcxixDY1L@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16634-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=16634

--- Comment #2 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, master has been updated
       via  a42faf59d6d9f82e5293a9ebcc26d9c9e562b12b (commit)
      from  509361270b4b889e991400a70eb87d45304c01cd (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

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

commit a42faf59d6d9f82e5293a9ebcc26d9c9e562b12b
Author: Paul Pluzhnikov <ppluzhnikov@google.com>
Date:   Mon Mar 24 10:58:26 2014 -0700

    Fix BZ #16634.

    An application that erroneously tries to repeatedly dlopen("a.out", ...)
    may hit assertion failure:

      Inconsistency detected by ld.so: dl-tls.c: 474: _dl_allocate_tls_init:
      Assertion `listp != ((void *)0)' failed!

    dlopen() actually fails with  "./a.out: cannot dynamically load
executable",
    but it does so after incrementing dl_tls_max_dtv_idx.

    Once we run out of TLS_SLOTINFO_SURPLUS (62), we exit with above assertion
    failure.

    2014-03-24  Paul Pluzhnikov  <ppluzhnikov@google.com>

        [BZ #16634]

        * elf/dl-load.c (open_verify): Add mode parameter.
            Error early when ET_EXEC and mode does not have __RTLD_OPENEXEC.
            (open_path): Change from boolean 'secure' to complete flag 'mode'
            (_dl_map_object): Adjust.
        * elf/Makefile (tests): Add tst-dlopen-aout.
        * elf/tst-dlopen-aout.c: New test.

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

Summary of changes:
 ChangeLog                                     |   11 ++++
 NEWS                                          |    6 +-
 elf/Makefile                                  |    3 +-
 elf/dl-load.c                                 |   36 +++++++++-----
 libio/test-freopen.c => elf/tst-dlopen-aout.c |   63 +++++++++++++-----------
 5 files changed, 74 insertions(+), 45 deletions(-)
 copy libio/test-freopen.c => elf/tst-dlopen-aout.c (51%)

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


  parent reply	other threads:[~2014-03-24 18:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26  0:52 [Bug dynamic-link/16634] New: " ppluzhnikov at google dot com
2014-02-26  0:56 ` [Bug dynamic-link/16634] " ppluzhnikov at google dot com
2014-03-24 18:14 ` cvs-commit at gcc dot gnu.org [this message]
2014-03-24 18:15 ` ppluzhnikov at google dot com
2014-06-13  6:47 ` 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-16634-131-8bcxixDY1L@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).