unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
To: Petr Vorel <pvorel@suse.cz>
Cc: libc-alpha@sourceware.org, Andreas Schwab <schwab@linux-m68k.org>
Subject: Re: Async cacellation and pthread_cleanup_push
Date: Mon, 23 Aug 2021 11:38:36 +0200	[thread overview]
Message-ID: <87y28sqz4z.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <YQzHzRlcHCNjwKs6@pevik> (Petr Vorel's message of "Fri, 6 Aug 2021 07:25:33 +0200")

* Petr Vorel:

> Hi Florian,
>
>> * Andreas Schwab:
>
>> > Is pthread_cleanup_push supposed to work together with async
>> > cancellation?
>
>> In our implementation?  I think so.  POSIX doesn't require it, though.
>
> Would you please share link to POSIX docs where it's stated?
> It'd help us to fix LTP POSIX tests.

Not sure if you seen my earlier comment:

[Section] 2.9.5 Thread Cancellation, Thread Cancellation Cleanup
Handlers and Async-Cancel Safety.  The first section calls
pthread_cleanup_push a function, the second section does not list it.

The section number refers to  POSIX.1-2017.

I hope this clarifies the matter.

Thanks,
Florian


  reply	other threads:[~2021-08-23  9:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04 13:58 Async cacellation and pthread_cleanup_push Andreas Schwab
2021-08-04 15:33 ` Florian Weimer via Libc-alpha
2021-08-04 16:04   ` Andreas Schwab
2021-08-04 16:10     ` Florian Weimer via Libc-alpha
2021-08-04 16:24       ` Andreas Schwab
2021-08-23  9:43         ` Florian Weimer via Libc-alpha
2021-08-23 10:05           ` Andreas Schwab
2021-08-23 10:11             ` Florian Weimer via Libc-alpha
2021-08-23 10:24               ` Andreas Schwab
2021-08-23 10:58                 ` Florian Weimer via Libc-alpha
2021-08-05 10:43       ` Petr Vorel
2021-08-06  5:25   ` Petr Vorel
2021-08-23  9:38     ` Florian Weimer via Libc-alpha [this message]
2021-08-23  9:49       ` Petr Vorel
2021-08-04 18:43 ` Zack Weinberg via Libc-alpha

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y28sqz4z.fsf@oldenburg.str.redhat.com \
    --to=libc-alpha@sourceware.org \
    --cc=fweimer@redhat.com \
    --cc=pvorel@suse.cz \
    --cc=schwab@linux-m68k.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).