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 libc/16831] Initialize _r_debug for static applications.
Date: Mon, 14 Apr 2014 20:06:00 -0000	[thread overview]
Message-ID: <bug-16831-131-KHG9fCeYYZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16831-131@http.sourceware.org/bugzilla/>

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

--- 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  f737dfd071f12584316ef90f2c71e33c2dc9801e (commit)
       via  0699f766b10c86912b75f35bef697106b70c1cf6 (commit)
      from  809bd45fa91992dd96aeb4dc4a58d471f9e0996c (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=f737dfd071f12584316ef90f2c71e33c2dc9801e

commit f737dfd071f12584316ef90f2c71e33c2dc9801e
Author: Carlos O'Donell <carlos@redhat.com>
Date:   Fri Apr 11 12:43:58 2014 -0400

    Support _r_debug for static binaries.

    We initialize _r_debug for static binaries to allows debug
    agents to treat static binaries a little more like dyanmic
    ones. This simplifies the work a debug agent has to do to
    access TLS in a static binary via libthread_db.

    Tested on x86_64.

    See:
    https://sourceware.org/ml/libc-alpha/2014-04/msg00183.html

        [BZ #16831]
        * csu/libc-start.c (LIBC_START_MAIN) [!SHARED]: Call
        _dl_debug_initialize.

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

commit 0699f766b10c86912b75f35bef697106b70c1cf6
Author: Carlos O'Donell <carlos@redhat.com>
Date:   Thu Apr 10 18:31:53 2014 -0400

    nscd: Make SELinux checks dynamic.

    The SELinux team has indicated to me that glibc's SELinux checks
    in nscd are not being carried out as they would expect the API
    to be used today. They would like to move away from static header
    defines for class and permissions and instead use dynamic checks
    at runtime that provide an answer which is dependent on the runtime
    status of SELinux i.e. more dynamic.

    The following patch is a minimal change that moves us forward in
    this direction.

    It does the following:

    * Stop checking for SELinux headers that define NSCD__SHMEMHOST.
      Check only for the presence or absence of the library.

    * Don't encode the specific SELinux permission constants into a
      table at build time, and instead use the symbolic name for the
      permission as expected.

    * Lookup the "What do we do if we don't know this permission?"
      policy and use that if we find SELinux's policy is older than
      the glibc policy e.g. we make a request for a permission that
      SELinux doesn't know about.

    * Lastly, translate the class and permission and then make
      the permission check. This is done every time we lookup
      a permission, and this is the expected way to use the API.
      SELinux will optimize this for us, and we expect the network
      latencies to hide these extra library calls.

    Tested on x86, x86-64, and via Fedora Rawhide since November 2013.

    See:
    https://sourceware.org/ml/libc-alpha/2014-04/msg00179.html

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

Summary of changes:
 ChangeLog        |   16 ++++++++
 NEWS             |    2 +-
 configure        |   31 +---------------
 configure.ac     |   15 +-------
 csu/libc-start.c |    3 ++
 nscd/selinux.c   |  107 ++++++++++++++++++++++++++++++++++--------------------
 6 files changed, 90 insertions(+), 84 deletions(-)

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


  parent reply	other threads:[~2014-04-14 20:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-11  0:33 [Bug libc/16831] New: " carlos at redhat dot com
2014-04-11  6:37 ` [Bug libc/16831] " jan.kratochvil at redhat dot com
2014-04-11  7:39 ` mjw at redhat dot com
2014-04-14 20:06 ` cvs-commit at gcc dot gnu.org [this message]
2014-04-15 11:00 ` gbenson at redhat dot com
2014-04-29 23:06 ` carlos at redhat dot com
2014-06-12 19:42 ` 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-16831-131-KHG9fCeYYZ@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).