Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: libvirt: fix deadlock for musl
Date: Sat, 02 Jan 2021 04:41:12 +0100	[thread overview]
Message-ID: <20210102034112.2Jif9l9P6foP79a8qDsyzwh94wgW3MOPxihC_13Iv_I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25905@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 727 bytes --]

There's a closed pull request on the void-packages repository

libvirt: fix deadlock for musl
https://github.com/void-linux/void-packages/pull/25905

Description:
libvirt has been broken under musl since v6.3 due to how it uses malloc/free after fork causing a deadlock. When libvirt is in this state, any attempt to connect to it (virsh/virt-manager) will just hangs forever waiting for connection until a `daemon-init` process under libvirt is killed (#23724, [alpine/aports#11602](https://gitlab.alpinelinux.org/alpine/aports/-/issues/11602), [libvirt/libvirt#52](https://gitlab.com/libvirt/libvirt/-/issues/52)).

This PR backport 2 patches from Alpine 3.12 to fix the issue. Going to need some testing on glibc, though.

      parent reply	other threads:[~2021-01-02  3:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26 22:45 [PR PATCH] " sirn
2020-10-26 22:52 ` [PR PATCH] [Updated] " sirn
2020-11-06 17:33 ` ahesford
2020-11-08 10:27 ` [PR PATCH] [Updated] " sirn
2020-11-08 10:36 ` sirn
2020-11-17 20:38 ` Logarithmus
2020-11-17 20:38 ` Logarithmus
2020-11-17 20:40 ` Logarithmus
2020-12-23 17:35 ` gch1p
2021-01-02  3:41 ` ahesford [this message]

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=20210102034112.2Jif9l9P6foP79a8qDsyzwh94wgW3MOPxihC_13Iv_I@z \
    --to=ahesford@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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 NNTP newsgroup(s).