linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gabriel Ravier <gabravier@gmail.com>
To: "Tomáš Golembiovský" <tgolembi@redhat.com>,
	"Alejandro Colomar" <alx@kernel.org>
Cc: linux-man@vger.kernel.org, Carlos O'Donell <carlos@redhat.com>,
	Glibc <libc-alpha@sourceware.org>
Subject: Re: [PATCH] abort.3: Note that the glibc implementation is not async-signal-safe
Date: Thu, 24 Aug 2023 23:07:00 +0100	[thread overview]
Message-ID: <45b86bac-faeb-b39a-6be4-5c5f1c4bdc6e@gmail.com> (raw)
In-Reply-To: <ZOThpIa46irPESgE@cremorrah>

On 8/22/23 17:26, Tomáš Golembiovský via Libc-alpha wrote:
> Hi,
>
> gentle reminder that this has not received any attention yet.
I assume this is because there are currently efforts to make glibc's 
implementation async-signal-safe - which would make this proposed note 
quite quickly inaccurate (though the fact it has been 
async-signal-unsafe until now still seems notable enough to be mentioned 
here).
>
> Thanks,
>
>      Tomas
>
> On Wed, Jul 26, 2023 at 01:55:27PM +0200, Tomáš Golembiovský wrote:
>> See https://sourceware.org/bugzilla/show_bug.cgi?id=26275
>>
>> Cc: Carlos O'Donell <carlos@redhat.com>
>> Cc: Glibc <libc-alpha@sourceware.org>
>> Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com>
>> ---
>>   man3/abort.3         | 6 ++++++
>>   man7/signal-safety.7 | 5 +++++
>>   2 files changed, 11 insertions(+)
>>
>> diff --git a/man3/abort.3 b/man3/abort.3
>> index 0b57e10ed..827d5c9db 100644
>> --- a/man3/abort.3
>> +++ b/man3/abort.3
>> @@ -85,6 +85,12 @@ terminates the process without flushing streams.
>>   POSIX.1 permits either possible behavior, saying that
>>   .BR abort ()
>>   "may include an attempt to effect fclose() on all open streams".
>> +.SH BUGS
>> +The glibc implementation of
>> +.BR abort ()
>> +is not async-signal-safe,
>> +.\" FIXME . https://sourceware.org/bugzilla/show_bug.cgi?id=26275
>> +in violation of the requirements of POSIX.1.
>>   .SH SEE ALSO
>>   .BR gdb (1),
>>   .BR sigaction (2),
>> diff --git a/man7/signal-safety.7 b/man7/signal-safety.7
>> index 3d6ddc7eb..431a22f89 100644
>> --- a/man7/signal-safety.7
>> +++ b/man7/signal-safety.7
>> @@ -335,6 +335,11 @@ The glibc implementation of
>>   is not async-signal-safe because it uses
>>   .BR pthread_mutex_lock (3)
>>   internally.
>> +.IP \[bu]
>> +.\" FIXME . https://sourceware.org/bugzilla/show_bug.cgi?id=26275
>> +The glibc implementation of
>> +.BR abort (3)
>> +is not async-signal-safe.
>>   .SH SEE ALSO
>>   .BR sigaction (2),
>>   .BR signal (7),
>> -- 
>> 2.41.0
>>


  reply	other threads:[~2023-08-24 22:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-26 11:55 [PATCH] abort.3: Note that the glibc implementation is not async-signal-safe Tomáš Golembiovský
2023-08-22 16:26 ` Tomáš Golembiovský
2023-08-24 22:07   ` Gabriel Ravier [this message]
2023-08-25 12:32     ` Tomáš Golembiovský
2023-08-25 17:53       ` Alejandro Colomar

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=45b86bac-faeb-b39a-6be4-5c5f1c4bdc6e@gmail.com \
    --to=gabravier@gmail.com \
    --cc=alx@kernel.org \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-man@vger.kernel.org \
    --cc=tgolembi@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 NNTP newsgroup(s).