public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
	Glibc hackers <libc-hacker@sources.redhat.com>,
	gjohnson@austin.ibm.com
Subject: Re: [PATCH] Avoid cancellation point in pthread_mutex_lock etc. in linuxthreads
Date: Wed, 02 Apr 2003 00:11:00 -0000	[thread overview]
Message-ID: <200304020011.h320B9O04232@magilla.sf.frob.com> (raw)
In-Reply-To: Jakub Jelinek's message of  Tuesday, 1 April 2003 17:19:26 +0200 <20030401151926.GI16629@sunsite.ms.mff.cuni.cz>

> linuxthreads call sigsuspend from pthread_mutex_lock etc., so when sigsuspend
> was made cancellation point in December, suddenly all pthread primitives
> which wait for restart signals are cancellation points.
> Fix below, tested on all the usual arches.

I put these in.

Thanks,
Roland

      parent reply	other threads:[~2003-04-02  0:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-01 15:19 Jakub Jelinek
2003-04-01 19:50 ` Roland McGrath
2003-04-01 20:17   ` Jakub Jelinek
2003-04-01 20:46     ` Ulrich Drepper
2003-04-02  0:11 ` Roland McGrath [this message]

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=200304020011.h320B9O04232@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=drepper@redhat.com \
    --cc=gjohnson@austin.ibm.com \
    --cc=jakub@redhat.com \
    --cc=libc-hacker@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).