From: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
To: Florian Weimer <fw@deneb.enyo.de>, Rich Felker <dalias@libc.org>
Cc: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>,
musl@lists.openwall.com
Subject: Re: [PATCH] Make abort() AS-safe (Bug 26275).
Date: Thu, 1 Oct 2020 10:49:42 -0400 [thread overview]
Message-ID: <ed7f2026-92e7-a8ba-a2b4-feb43817b2e3@redhat.com> (raw)
In-Reply-To: <87o8lmeaw7.fsf@mid.deneb.enyo.de>
On 10/1/20 2:08 AM, Florian Weimer wrote:
> * Rich Felker:
>
>> Even without fork, execve and posix_spawn can also see the SIGABRT
>> disposition change made by abort(), passing it on to a process that
>> should have started with a disposition of SIG_IGN if you hit exactly
>> the wrong spot in the race.
>
> My feeling is that it's not worth bothering with this kind of leakage.
> We've had this bug forever in glibc, and no one has complained about
> it.
>
> Carlos is investigating removal of the abort lock from glibc, I think.
I am investigating the removal, but I think the replacement solution
might be needing to have a helper thread carry out specific tasks.
Like Rich I'm still a little worried about the other cases that the
lock is intended to fix.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2020-10-01 14:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 14:19 [PATCH] Make abort() AS-safe (Bug 26275) Carlos O'Donell via Libc-alpha
2020-09-27 20:04 ` Florian Weimer
2020-09-28 23:48 ` Rich Felker
2020-09-29 6:54 ` Florian Weimer
2020-09-29 14:42 ` Rich Felker
2020-10-01 2:30 ` Rich Felker
2020-10-01 6:08 ` Florian Weimer
2020-10-01 14:39 ` [musl] " Rich Felker
2020-10-01 15:11 ` Florian Weimer via Libc-alpha
2020-10-01 15:28 ` Rich Felker
2020-10-01 14:49 ` Carlos O'Donell via Libc-alpha [this message]
2020-10-01 14:55 ` Rich Felker
2020-10-10 0:26 ` Rich Felker
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=ed7f2026-92e7-a8ba-a2b4-feb43817b2e3@redhat.com \
--to=libc-alpha@sourceware.org \
--cc=carlos@redhat.com \
--cc=dalias@libc.org \
--cc=fw@deneb.enyo.de \
--cc=musl@lists.openwall.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).