From: Laurent Vivier <laurent@vivier.eu>
To: "Mathis Marion" <Mathis.Marion@silabs.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org, "Jérôme Pouiller" <jerome.pouiller@silabs.com>
Subject: Re: [PATCH v3 1/2] linux-user: fix sockaddr_in6 endianness
Date: Tue, 7 Mar 2023 16:59:07 +0100 [thread overview]
Message-ID: <b42db7d5-b8f9-ec6f-e47d-bf67d1db9471@vivier.eu> (raw)
In-Reply-To: <20230307154256.101528-2-Mathis.Marion@silabs.com>
Le 07/03/2023 à 16:42, Mathis Marion a écrit :
> From: Mathis Marion <mathis.marion@silabs.com>
>
> The sin6_scope_id field uses the host byte order, so there is a
> conversion to be made when host and target endianness differ.
>
> Signed-off-by: Mathis Marion <mathis.marion@silabs.com>
> ---
> linux-user/syscall.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
> index 247e20572d..bafa77d353 100644
> --- a/linux-user/syscall.c
> +++ b/linux-user/syscall.c
> @@ -1713,6 +1713,11 @@ static inline abi_long target_to_host_sockaddr(int fd, struct sockaddr *addr,
> lladdr = (struct target_sockaddr_ll *)addr;
> lladdr->sll_ifindex = tswap32(lladdr->sll_ifindex);
> lladdr->sll_hatype = tswap16(lladdr->sll_hatype);
> + } else if (sa_family == AF_INET6) {
> + struct sockaddr_in6 *in6addr;
> +
> + in6addr = (struct sockaddr_in6 *)addr;
> + in6addr->sin6_scope_id = tswap32(in6addr->sin6_scope_id);
> }
> unlock_user(target_saddr, target_addr, 0);
>
Reviewed-by: Laurent Vivier <laurent@vivier.eu>
next prev parent reply other threads:[~2023-03-07 15:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 15:42 [PATCH v3 0/2] Missing endianness conversions in user mode Mathis Marion
2023-03-07 15:42 ` [PATCH v3 1/2] linux-user: fix sockaddr_in6 endianness Mathis Marion
2023-03-07 15:59 ` Laurent Vivier [this message]
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=b42db7d5-b8f9-ec6f-e47d-bf67d1db9471@vivier.eu \
--to=laurent@vivier.eu \
--cc=Mathis.Marion@silabs.com \
--cc=jerome.pouiller@silabs.com \
--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 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).