From: richfelker <richfelker@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: qemu-aarch64-static works in glibc but the musl version is missing certain network functions.
Date: Thu, 29 Oct 2020 07:32:46 +0100 [thread overview]
Message-ID: <20201029063246.ieYcX0f85n6Zh1SUsi_HK2ncxYclBOvZjvRyQZlbiNQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23557@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
New comment by richfelker on void-packages repository
https://github.com/void-linux/void-packages/issues/23557#issuecomment-718392360
Comment:
OK, this turned out to be from `sendmsg` failing with `EMSGSIZE`, which is part of a systemic issue of qemu `linux-user/syscall.c` mixing libc types and raw syscalls. This was introduced in 2016 as part of "safe syscalls" for fixing interaction of emulated syscalls with signals, and the fix basically precluded ever being able to run qemu linux-user guest on non-linux host, and made it hard to run even on a linux host if the libc and kernel uapi types don't entirely match.
Working around the `sendmsg` problem is fairly easy just by making `do_sendrecvmsg_locked` zero-initialize its `struct msghdr`, but there are a large number of othe `safe_*` calls in that file that are making invalid assumptions about libc and kernel types matching, especially in the way of time64 breakage.
next prev parent reply other threads:[~2020-10-29 6:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 3:42 [ISSUE] " ejolson2005
2020-07-14 3:44 ` ericonr
2020-07-14 3:51 ` ejolson2005
2020-07-14 3:52 ` ejolson2005
2020-07-14 3:52 ` ejolson2005
2020-07-14 3:55 ` ejolson2005
2020-07-14 4:00 ` ejolson2005
2020-07-18 5:24 ` sgn
2020-10-29 2:31 ` ericonr
2020-10-29 2:48 ` richfelker
2020-10-29 5:13 ` ericonr
2020-10-29 6:32 ` richfelker [this message]
2021-02-11 18:22 ` [ISSUE] [CLOSED] " ericonr
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=20201029063246.ieYcX0f85n6Zh1SUsi_HK2ncxYclBOvZjvRyQZlbiNQ@z \
--to=richfelker@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).