From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.3 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 27057 invoked from network); 15 Aug 2020 11:51:19 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 15 Aug 2020 11:51:19 -0000 Received: (qmail 32021 invoked by uid 550); 15 Aug 2020 11:51:15 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 31997 invoked from network); 15 Aug 2020 11:51:14 -0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\)) From: Natanael Copa In-Reply-To: <20200815095124.526ce794@vostro.wlan> Date: Sat, 15 Aug 2020 13:51:00 +0200 Cc: Rich Felker Content-Transfer-Encoding: quoted-printable Message-Id: <07D76F82-52CF-4CA1-9D6C-B30A94F728B1@alpinelinux.org> References: <20200814214136.GP3265@brightrain.aerifal.cx> <20200815095124.526ce794@vostro.wlan> To: musl@lists.openwall.com X-Mailer: Apple Mail (2.3608.120.23.2.1) Subject: Re: [musl] Restrictions on child context after multithreaded fork > 15. aug. 2020 kl. 08:51 skrev Timo Teras : >=20 > On Fri, 14 Aug 2020 17:41:38 -0400 > Rich Felker wrote: >=20 >> 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: >>=20 >> https://gitlab.alpinelinux.org/alpine/aports/-/issues/11602 >> https://gitlab.alpinelinux.org/alpine/aports/-/issues/11815 >=20 > Add to that list glib and libvte. >=20 > 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 >=20 > 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. >=20 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=3Dad687b01b2a5= fa9d53fcd9d0ee3743882f3542b4 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=3D161434fcb878= 07dae40dffdd332db1624b747bc7 After that xfce4-terminal becomes useable again. -nc