mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Natanael Copa <ncopa@alpinelinux.org>
To: musl@lists.openwall.com
Cc: Rich Felker <dalias@libc.org>
Subject: Re: [musl] Restrictions on child context after multithreaded fork
Date: Sat, 15 Aug 2020 13:51:00 +0200	[thread overview]
Message-ID: <07D76F82-52CF-4CA1-9D6C-B30A94F728B1@alpinelinux.org> (raw)
In-Reply-To: <20200815095124.526ce794@vostro.wlan>



> 15. aug. 2020 kl. 08:51 skrev Timo Teras <timo.teras@iki.fi>:
> 
> On Fri, 14 Aug 2020 17:41:38 -0400
> Rich Felker <dalias@libc.org> 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:
>> 
>> https://gitlab.alpinelinux.org/alpine/aports/-/issues/11602
>> https://gitlab.alpinelinux.org/alpine/aports/-/issues/11815
> 
> 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:
> https://gitlab.gnome.org/GNOME/glib/-/issues/2140
> 
> Unfortunately, libvte duplicates the some of the code and the issue:
> there's https://gitlab.gnome.org/GNOME/vte/-/issues/263
> 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:
https://git.alpinelinux.org/aports/commit/community/vte3?id=ad687b01b2a5fa9d53fcd9d0ee3743882f3542b4

In the second patch I use some of the hunks in the upstream and replace malloc with alloca:
https://git.alpinelinux.org/aports/commit/community/vte3?id=161434fcb87807dae40dffdd332db1624b747bc7

After that xfce4-terminal becomes useable again.


-nc



  reply	other threads:[~2020-08-15 11:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-14 21:41 Rich Felker
2020-08-14 22:02 ` Florian Weimer
2020-08-14 22:14   ` Rich Felker
2020-08-15  0:47 ` A. Wilcox
2020-08-15  2:40   ` Rich Felker
2020-08-15  2:07 ` Ariadne Conill
2020-08-15  3:02   ` Rich Felker
2020-08-15  6:51 ` Timo Teras
2020-08-15 11:51   ` Natanael Copa [this message]
2020-08-15 16:25     ` Rich Felker
2020-08-16  1:27       ` Rich Felker
2020-08-16 12:48         ` Natanael Copa
2020-08-16  3:57 ` Rich Felker
2020-08-16  9:10   ` Florian Weimer
2020-08-16 16:56     ` Rich Felker
2020-08-16 17:11       ` Florian Weimer
2020-08-16 18:33         ` Rich Felker
2020-08-16  7:05 ` Pirmin Walthert
2020-08-16 16:55   ` Rich Felker
2020-09-30 18:38 ` 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

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

  git send-email \
    --in-reply-to=07D76F82-52CF-4CA1-9D6C-B30A94F728B1@alpinelinux.org \
    --to=ncopa@alpinelinux.org \
    --cc=dalias@libc.org \
    --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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).