Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 15 Aug 2020 13:51:00 +0200
From: Natanael Copa <>
Cc: Rich Felker <>
Subject: Re: Restrictions on child context after multithreaded fork

> 15. aug. 2020 kl. 08:51 skrev Timo Teras <>:
> On Fri, 14 Aug 2020 17:41:38 -0400
> Rich Felker <> wrote:
>> musl 1.2.1 has exposed bugs in several applications and libraries
>> caused by async-signal-unsafe code between (multithreaded) fork and
>> subsequent exec. So far, dbus library code, pulseaudio library code,
>> and libvirt have been found to be affected. A couple of the bug
>> reports (with incomplete information) are:
> Add to that list glib and libvte.
> XFCE4 became quite unusable due to glib. Fortunately, it was fixed
> quite fast, and is merged for Alpine already:
> Unfortunately, libvte duplicates the some of the code and the issue:
> there's
> That got fixed relatively fast too in git master, but is not backported
> to any stables branch. So that's not merged yet in Alpine. And is
> causing still random lock ups in e.g. xfce4-terminal.

xfce4-terminal was more or less completely useless so I had to add a workaround for it in two patches:

First uncover a useless setenv. Even the comment in the code says that it has no effect:

In the second patch I use some of the hunks in the upstream and replace malloc with alloca:

After that xfce4-terminal becomes useable again.


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.