public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drow at sources dot redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nptl/3270] Setuid implementation has races and lockups
Date: Wed, 27 Sep 2006 15:38:00 -0000 [thread overview]
Message-ID: <20060927153834.15637.qmail@sourceware.org> (raw)
In-Reply-To: <20060927153710.3270.drow@sources.redhat.com>
------- Additional Comments From drow at sources dot redhat dot com 2006-09-27 15:38 -------
Created an attachment (id=1329)
--> (http://sourceware.org/bugzilla/attachment.cgi?id=1329&action=view)
Testcase.
This test illustrates the problem, but not reliably. I have to run about
twenty copies of it in parallel; some of them will exit after 3000 iterations,
others will remain blocked with one thread in pthread_join.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=3270
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2006-09-27 15:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 15:37 [Bug nptl/3270] New: " drow at sources dot redhat dot com
2006-09-27 15:38 ` drow at sources dot redhat dot com [this message]
2006-09-27 15:41 ` [Bug nptl/3270] " drow at sources dot redhat dot com
2007-12-15 9:48 ` ismail at pardus dot org dot tr
2008-02-12 22:34 ` pwatkins at sicortex dot com
2008-12-05 14:22 ` vincent dot arrat at infotel dot com
2008-12-05 16:01 ` pasky at suse dot cz
2009-10-29 16:54 ` schwab at linux-m68k dot org
2009-10-29 16:55 ` schwab at linux-m68k dot org
2009-10-30 8:01 ` drepper at redhat dot com
[not found] <bug-3270-131@http.sourceware.org/bugzilla/>
2014-04-15 23:01 ` wade.colson at aol dot com
2014-07-01 20:28 ` 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=20060927153834.15637.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.com \
/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).