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/13347] Threaded setuid() can wrongly report success when failing to drop privileges Date: Tue, 01 Apr 2014 10:13:00 -0000 [thread overview] Message-ID: <bug-13347-131-OoPUTZjRRg@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13347-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=13347 --- Comment #9 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 13f7fe35ae2b0ea55dc4b9628763aafdc8bdc30c (commit) from c859b32e9d76afe8a3f20bb9528961a573c06937 (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=13f7fe35ae2b0ea55dc4b9628763aafdc8bdc30c commit 13f7fe35ae2b0ea55dc4b9628763aafdc8bdc30c Author: Florian Weimer <fweimer@redhat.com> Date: Mon Mar 24 15:24:02 2014 +0100 Check for syscall error in the SETXID implementation in NPTL (bug 13347). At this point, we can only abort the process because we have already switched credentials on other threads. Returning an error would still leave the process in an inconsistent state. The new xtest needs root privileges to run. ----------------------------------------------------------------------- Summary of changes: ChangeLog | 7 +++ nptl/Makefile | 3 +- nptl/nptl-init.c | 9 +++- nptl/tst-setuid2.c | 145 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 161 insertions(+), 3 deletions(-) create mode 100644 nptl/tst-setuid2.c -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-04-01 10:13 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-26 3:33 [Bug nptl/13347] New: " bugdal at aerifal dot cx 2012-03-17 20:38 ` [Bug nptl/13347] " bugdal at aerifal dot cx 2012-04-29 3:03 ` bugdal at aerifal dot cx 2012-04-29 17:00 ` ppluzhnikov at google dot com 2012-07-24 14:52 ` carlos_odonell at mentor dot com 2012-07-24 14:56 ` fweimer at redhat dot com 2012-07-24 18:15 ` bugdal at aerifal dot cx 2012-07-24 18:35 ` carlos_odonell at mentor dot com 2012-07-24 23:04 ` bugdal at aerifal dot cx 2012-07-25 2:20 ` carlos_odonell at mentor dot com 2012-12-03 23:57 ` carlos at systemhalted dot org 2014-03-24 13:57 ` fweimer at redhat dot com 2014-03-24 15:19 ` bugdal at aerifal dot cx 2014-03-24 18:32 ` carlos at redhat dot com 2014-04-01 10:13 ` cvs-commit at gcc dot gnu.org [this message] 2014-04-01 11:54 ` joseph at codesourcery dot com 2014-04-01 12:21 ` fweimer at redhat dot com 2014-04-01 12:21 ` cvs-commit at gcc dot gnu.org 2014-06-27 11:43 ` fweimer at redhat dot com 2014-06-27 13:15 ` bugdal at aerifal dot cx 2014-07-09 10:26 ` fweimer at redhat dot com 2014-07-22 12:35 ` fweimer at redhat dot com 2014-07-22 12:57 ` bugdal at aerifal dot cx
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-13347-131-OoPUTZjRRg@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: linkBe 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).