Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 1 Oct 2020 10:49:42 -0400
From: Carlos O'Donell <>
To: Florian Weimer <>, Rich Felker <>
 Carlos O'Donell via Libc-alpha <>
Subject: Re: [PATCH] Make abort() AS-safe (Bug 26275).

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.


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.