From: Mathis Marion <Mathis.Marion@silabs.com>
To: "Laurent Vivier" <laurent@vivier.eu>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org,
"Jérôme Pouiller" <jerome.pouiller@silabs.com>,
"Mathis Marion" <mathis.marion@silabs.com>
Subject: [PATCH v3 0/2] Missing endianness conversions in user mode
Date: Tue, 7 Mar 2023 16:42:54 +0100 [thread overview]
Message-ID: <20230307154256.101528-1-Mathis.Marion@silabs.com> (raw)
From: Mathis Marion <mathis.marion@silabs.com>
For a bit of context, I was trying to test a network border router [1]
daemon using the MIPS architecture (see [2]). I didn't have access to
real MIPS hardware so I figured I would emulate it using QEMU user mode.
I ran into a couple of problems all related to endianness conversion for
syscalls between host and target as MIPS is big endian and my x86 host
is little.
[1]: https://github.com/SiliconLabs/wisun-br-linux
[2]: https://github.com/SiliconLabs/wisun-br-linux/issues/5
v3:
- remove patches "linux-user: fix timerfd read endianness conversion"
and "linux-user: add target to host netlink conversions" as they were
integrated.
- remove sin6_flowinfo endianness conversion
- use NLA_TYPE_MASK instead of ~NLA_F_NESTED
v2:
- remove context from target_to_host_for_each_nlattr()
Mathis Marion (2):
linux-user: fix sockaddr_in6 endianness
linux-user: handle netlink flag NLA_F_NESTED
linux-user/fd-trans.c | 4 ++--
linux-user/syscall.c | 5 +++++
2 files changed, 7 insertions(+), 2 deletions(-)
--
2.39.2
next reply other threads:[~2023-03-07 15:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 15:42 Mathis Marion [this message]
2023-03-07 15:42 ` [PATCH v3 1/2] linux-user: fix sockaddr_in6 endianness Mathis Marion
2023-03-07 15:59 ` Laurent Vivier
2023-03-07 16:07 ` Laurent Vivier
2023-03-07 16:28 ` Philippe Mathieu-Daudé
2023-03-07 15:42 ` [PATCH v3 2/2] linux-user: handle netlink flag NLA_F_NESTED Mathis Marion
2023-03-07 16:00 ` Laurent Vivier
2023-03-07 16:08 ` Laurent Vivier
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=20230307154256.101528-1-Mathis.Marion@silabs.com \
--to=mathis.marion@silabs.com \
--cc=jerome.pouiller@silabs.com \
--cc=laurent@vivier.eu \
--cc=philmd@linaro.org \
--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.