From: Laurent Vivier <laurent@vivier.eu>
To: "Mathis MARION" <mamarion1@silabs.com>,
"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 v2 2/4] linux-user: fix sockaddr_in6 endianness
Date: Tue, 7 Mar 2023 14:37:28 +0100 [thread overview]
Message-ID: <baa0d31c-ffba-c619-e90a-9e4596342be0@vivier.eu> (raw)
In-Reply-To: <5af1e768-820a-68d4-5d98-e4b6fbcc7d90@silabs.com>
Le 07/03/2023 à 12:27, Mathis MARION a écrit :
>
>
> On 06/03/2023 22:52, Laurent Vivier wrote:
>> CAUTION: This email originated from outside of the organization. Do not click links or open
>> attachments unless you recognize the sender and know the content is safe.
>>
>>
>> Le 20/02/2023 à 09:58, Mathis Marion a écrit :
>>> From: Mathis Marion <mathis.marion@silabs.com>
>>>
>>> Fields sin6_flowinfo and sin6_scope_id use 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 | 6 ++++++
>>> 1 file changed, 6 insertions(+)
>>>
>>> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
>>> index 58549de125..1a6856abec 100644
>>> --- a/linux-user/syscall.c
>>> +++ b/linux-user/syscall.c
>>> @@ -1713,6 +1713,12 @@ 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_flowinfo = tswap32(in6addr->sin6_flowinfo);
>>
>> In /usr/include/linux/in6.h, it's defined as a __be32, so I don't think we need to change its
>> endianness.
>>
>
> Right.
> Thank you for integrating the other patches! Before I send a v3, do you
> have any comments on patch 4?
>
Yes, use *_MASK rather than ~*_NESTED. It looks cleaner. I prefer to ignore flags rather than return
an error, so on architectures with same endiannes/wordsize it generally works.
Thanks,
Laurent
next prev parent reply other threads:[~2023-03-07 13:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 8:58 [PATCH v2 0/4] Missing endianness conversions in user mode Mathis Marion
2023-02-20 8:58 ` [PATCH v2 1/4] linux-user: fix timerfd read endianness conversion Mathis Marion
2023-03-06 21:42 ` Laurent Vivier
2023-03-07 9:33 ` Laurent Vivier
2023-02-20 8:58 ` [PATCH v2 2/4] linux-user: fix sockaddr_in6 endianness Mathis Marion
2023-02-20 9:06 ` Philippe Mathieu-Daudé
2023-02-20 9:09 ` Mathis MARION
2023-02-20 9:32 ` Philippe Mathieu-Daudé
2023-03-06 21:52 ` Laurent Vivier
2023-03-07 11:27 ` Mathis MARION
2023-03-07 13:37 ` Laurent Vivier [this message]
2023-02-20 8:58 ` [PATCH v2 3/4] linux-user: add target to host netlink conversions Mathis Marion
2023-02-20 9:04 ` Philippe Mathieu-Daudé
2023-03-06 22:02 ` Laurent Vivier
2023-03-07 9:32 ` Laurent Vivier
2023-02-20 8:58 ` [PATCH v2 4/4] linux-user: handle netlink flag NLA_F_NESTED Mathis Marion
2023-02-20 9:15 ` Mathis MARION
2023-04-01 9:19 ` [PATCH v2 0/4] Missing endianness conversions in user mode Michael Tokarev
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=baa0d31c-ffba-c619-e90a-9e4596342be0@vivier.eu \
--to=laurent@vivier.eu \
--cc=Mathis.Marion@silabs.com \
--cc=jerome.pouiller@silabs.com \
--cc=mamarion1@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).