public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjmunroe at us dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nptl/2748] New: Cancel from printf not calling the cancel handler
Date: Fri, 09 Jun 2006 22:10:00 -0000	[thread overview]
Message-ID: <20060609220957.2748.sjmunroe@us.ibm.com> (raw)

Found this problem debug failure reported by our cluster team. If we are
PTHREAD_CANCEL_ENABLE, PTHREAD_CANCEL_DEFERRED and pthread_cancel is called
while a thread is waiting on a pthread_rwlock the cancelation will be defered
until the threads wakes up (whoever is holding the lock does
pthread_rwlock_unlock(). 

In this case the thread holding the lock is signaled, runs its cancle handler
and unlocks. One of the waiting threads wakes up and calls printf (which is a
cancellation point). We expect printf (vfprintf) to detect that cancellation is
pending and initiate cancel handling (including calling this threads cancel
handler).

Instead we that thread exiting prematurely (from start_thread,
__exit_thread_inline(0). This leave other threads hung waiting on the
pthread_rwlock and the main thread waiting on pthread_join.

-- 
           Summary: Cancel from printf not calling the cancel handler
           Product: glibc
           Version: 2.4
            Status: NEW
          Severity: critical
          Priority: P1
         Component: nptl
        AssignedTo: drepper at redhat dot com
        ReportedBy: sjmunroe at us dot ibm dot com
                CC: glibc-bugs at sources dot redhat dot com
 GCC build triplet: i568-unknown-linux-gnu, powerpc64-unknown-linux-gnu,
                    powerpc32-u
  GCC host triplet: i568-unknown-linux-gnu, powerpc64-unknown-linux-gnu,
                    powerpc32-u
GCC target triplet: i568-unknown-linux-gnu, powerpc64-unknown-linux-gnu,
                    powerpc32-u


http://sourceware.org/bugzilla/show_bug.cgi?id=2748

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2006-06-09 22:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-09 22:10 sjmunroe at us dot ibm dot com [this message]
2006-06-09 22:13 ` [Bug nptl/2748] " sjmunroe at us dot ibm dot com
2006-06-09 22:18 ` sjmunroe at us dot ibm dot com
2006-06-09 22:27 ` sjmunroe at us dot ibm dot com
2006-06-13 21:45 ` bergner at vnet dot ibm dot com
2006-06-13 21:46 ` bergner at vnet dot ibm dot com
2006-08-13  6:38 ` drepper at redhat dot com
2006-08-13  6:39 ` drepper at redhat dot com
2006-08-13  6:39 ` drepper at redhat dot com
2007-03-28 16:18 ` jakub at redhat dot com
2007-03-28 16:19 ` jakub at redhat dot com
2007-03-29 14:53 ` sjmunroe at us dot ibm dot com
2008-04-08  1:18 ` drepper at redhat dot com
2010-06-01  2:26 ` pasky at suse dot cz

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=20060609220957.2748.sjmunroe@us.ibm.com \
    --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).