From: Laurent Vivier <Laurent@vivier.eu>
To: qemu-devel@nongnu.org
Subject: [Bug 1823790] Re: QEMU mishandling of SO_PEERSEC forces systemd into tight loop
Date: Thu, 30 Apr 2020 13:36:05 -0000 [thread overview]
Message-ID: <158825376581.12757.6317159222253950337.malone@wampee.canonical.com> (raw)
In-Reply-To: 155475569461.20468.17957138207618410360.malonedeb@chaenomeles.canonical.com
Fixed here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=6d485a55d0cd
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1823790
Title:
QEMU mishandling of SO_PEERSEC forces systemd into tight loop
Status in QEMU:
Fix Released
Bug description:
While building Debian images for embedded ARM target systems I
detected that QEMU seems to force newer systemd daemons into a tight
loop.
My setup is the following:
Host machine: Ubuntu 18.04, amd64
LXD container: Debian Buster, arm64, systemd 241
QEMU: qemu-aarch64-static, 4.0.0-rc2 (custom build) and 3.1.0 (Debian 1:3.1+dfsg-7)
To easily reproduce the issue I have created the following repository:
https://github.com/lueschem/edi-qemu
The call where systemd gets looping is the following:
2837 getsockopt(3,1,31,274891889456,274887218756,274888927920) = -1 errno=34 (Numerical result out of range)
Furthermore I also verified that the issue is not related to LXD.
The same behavior can be reproduced using systemd-nspawn.
This issue reported against systemd seems to be related:
https://github.com/systemd/systemd/issues/11557
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1823790/+subscriptions
next prev parent reply other threads:[~2020-04-30 14:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 20:34 [Qemu-devel] [Bug 1823790] [NEW] QEMU forces systemd into tight loop Matthias Lüscher
2019-04-09 13:14 ` [Qemu-devel] [Bug 1823790] " Peter Maydell
2019-04-09 13:26 ` [Qemu-devel] [Bug 1823790] Re: QEMU mishandling of SO_PEERSEC " Peter Maydell
2019-04-11 20:36 ` Matthias Lüscher
2019-04-11 20:52 ` Matthias Lüscher
2019-08-16 6:46 ` Fritz Katze
2019-08-16 9:05 ` Fritz Katze
2020-01-29 6:20 ` Tobias Koch
2020-01-29 6:52 ` Tobias Koch
2020-01-31 15:40 ` Laurent Vivier
2020-01-31 20:51 ` Laurent Vivier
2020-02-03 13:54 ` Matthias Lüscher
2020-02-03 8:07 ` Tobias Koch
2020-02-04 12:51 ` Tobias Koch
2020-02-08 12:03 ` zebul666
2020-02-20 6:56 ` Charlie Sharpsteen
2020-02-20 12:21 ` Laurent Vivier
2020-04-30 13:36 ` Laurent Vivier [this message]
2020-08-18 14:04 ` Christian Ehrhardt
2020-08-18 14:05 ` Christian Ehrhardt
2020-08-24 16:24 ` Steve Dodd
2020-08-27 16:54 ` Charlie Sharpsteen
2020-08-28 20:14 ` Laurent Vivier
2020-08-28 21:03 ` Laurent Vivier
2020-09-20 18:06 ` Charlie Sharpsteen
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=158825376581.12757.6317159222253950337.malone@wampee.canonical.com \
--to=laurent@vivier.eu \
--cc=1823790@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.