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 nptl/17135] setxid wrapper changes cause process aborts
Date: Fri, 11 Jul 2014 10:32:00 -0000	[thread overview]
Message-ID: <bug-17135-131-1BdtOuCZuf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17135-131@http.sourceware.org/bugzilla/>

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

--- Comment #1 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  771eb1415fde935e377111f69364a5d92a29e67d (commit)
      from  bc1da1765e901a9a9f532f91d09f5237655e01fd (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=771eb1415fde935e377111f69364a5d92a29e67d

commit 771eb1415fde935e377111f69364a5d92a29e67d
Author: Florian Weimer <fweimer@redhat.com>
Date:   Thu Jul 10 17:34:46 2014 +0200

    nptl: Fix abort in case of set*id failure [BZ #17135]

    If a call to the set*id functions fails in a multi-threaded program,
    the abort introduced in commit 13f7fe35ae2b0ea55dc4b9628763aafdc8bdc30c
    was triggered.

    We address by checking that all calls to set*id on all threads give
    the same result, and only abort if we see success followed by failure
    (or vice versa).

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

Summary of changes:
 ChangeLog            |   12 ++++++
 NEWS                 |    2 +-
 nptl/Makefile        |    1 +
 nptl/allocatestack.c |   27 ++++++++++++-
 nptl/descr.h         |    1 +
 nptl/nptl-init.c     |    6 +-
 nptl/pthreadP.h      |    2 +
 nptl/tst-setuid3.c   |  104 ++++++++++++++++++++++++++++++++++++++++++++++++++
 8 files changed, 149 insertions(+), 6 deletions(-)
 create mode 100644 nptl/tst-setuid3.c

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


  parent reply	other threads:[~2014-07-11 10:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09 10:25 [Bug nptl/17135] New: " fweimer at redhat dot com
2014-07-09 10:26 ` [Bug nptl/17135] " fweimer at redhat dot com
2014-07-09 10:26 ` fweimer at redhat dot com
2014-07-10 15:36 ` fweimer at redhat dot com
2014-07-11 10:32 ` cvs-commit at gcc dot gnu.org [this message]
2014-07-11 10:33 ` 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-17135-131-1BdtOuCZuf@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).