From: Laurent Vivier <laurent@vivier.eu>
To: Helge Deller <deller@gmx.de>, qemu-devel@nongnu.org
Cc: Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] linux-user: Add missing IPV6 sockopts
Date: Wed, 6 Mar 2019 14:05:46 +0100 [thread overview]
Message-ID: <e6a8123c-20f9-8cc4-594f-8db02c3607cc@vivier.eu> (raw)
In-Reply-To: <20190227191556.GA20198@ls3530.dellerweb.de>
On 27/02/2019 20:15, Helge Deller wrote:
> When running ssh over IPv6 with linux-user I faced this warning:
> Unsupported setsockopt level=41 optname=67
> setsockopt IPV6_TCLASS 32: Protocol not available:
>
> This patch adds a few missing IPV6 options, including IPV6_TCLASS.
>
> Signed-off-by: Helge Deller <deller@gmx.de>
>
> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
> index 5bbb72f3d5..08efbf14b6 100644
> --- a/linux-user/syscall.c
> +++ b/linux-user/syscall.c
> @@ -1871,6 +1874,20 @@ static abi_long do_setsockopt(int sockfd, int level, int optname,
> case IPV6_RECVHOPLIMIT:
> case IPV6_2292HOPLIMIT:
> case IPV6_CHECKSUM:
> + case IPV6_ADDRFORM:
> + case IPV6_2292PKTINFO:
> + case IPV6_RECVTCLASS:
> + case IPV6_RECVRTHDR:
> + case IPV6_2292RTHDR:
> + case IPV6_RECVHOPOPTS:
> + case IPV6_2292HOPOPTS:
> + case IPV6_RECVDSTOPTS:
> + case IPV6_2292DSTOPTS:
> + case IPV6_TCLASS:
> + case IPV6_RECVPATHMTU:
> + case IPV6_TRANSPARENT:
> + case IPV6_FREEBIND:
> + case IPV6_RECVORIGDSTADDR:
> val = 0;
> if (optlen < sizeof(uint32_t)) {
> return -TARGET_EINVAL;
>
It looks good. Could you also update do_getsockopt() list?
Thanks,
Laurent
next prev parent reply other threads:[~2019-03-06 13:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 19:15 [Qemu-devel] [PATCH] linux-user: Add missing IPV6 sockopts Helge Deller
2019-03-06 13:05 ` Laurent Vivier [this message]
2019-03-10 11:12 ` [Qemu-devel] [PATCH v2] " Helge Deller
2019-03-10 16:01 ` Laurent Vivier
2019-03-10 16:22 ` 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=e6a8123c-20f9-8cc4-594f-8db02c3607cc@vivier.eu \
--to=laurent@vivier.eu \
--cc=deller@gmx.de \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).