qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@gnu.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "J. Kiszka" <jan.kiszka@siemens.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/5] ipv4-only and ipv6-only support
Date: Thu, 31 Mar 2016 16:49:41 +0200	[thread overview]
Message-ID: <20160331144941.GT2636@var.bordeaux.inria.fr> (raw)
In-Reply-To: <CAFEAcA8=pbV_2OKmqmL+i9SuQ4zrz1b_8MaMYDh8WEa6MZVn8g@mail.gmail.com>

Peter Maydell, on Thu 31 Mar 2016 15:44:13 +0100, wrote:
>                  if (get_dns6_addr(&sin6->sin6_addr,
> &sin6->sin6_scope_id) < 0) {
>                  ^
> In file included from /home/petmay01/linaro/qemu-for-merges/slirp/slirp.h:99:0,
>                  from /home/petmay01/linaro/qemu-for-merges/slirp/socket.c:10:
> /home/petmay01/linaro/qemu-for-merges/slirp/libslirp.h:10:5: note:
> expected ‘uint32_t *’ but argument is of type ‘u_long *’

Urgl, so Windows is again not posix-compliant here... I guess the least
ugly workaround is as below.

Samuel

diff --git a/slirp/socket.c b/slirp/socket.c
index 896c27e..3d3c72a 100644
--- a/slirp/socket.c
+++ b/slirp/socket.c
@@ -796,7 +796,10 @@ void sotranslate_out(struct socket *so, struct sockaddr_storage *addr)
         if (in6_equal_net(&so->so_faddr6, &slirp->vprefix_addr6,
                     slirp->vprefix_len)) {
             if (in6_equal(&so->so_faddr6, &slirp->vnameserver_addr6)) {
-                if (get_dns6_addr(&sin6->sin6_addr, &sin6->sin6_scope_id) < 0) {
+                uint32_t scope_id;
+                if (get_dns6_addr(&sin6->sin6_addr, &scope_id) >= 0) {
+                    sin6->sin6_scope_id = scope_id;
+                } else {
                     sin6->sin6_addr = in6addr_loopback;
                 }
             } else {

      reply	other threads:[~2016-03-31 14:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-31  9:20 [Qemu-devel] [PULL 0/5] ipv4-only and ipv6-only support Samuel Thibault
2016-03-31  9:20 ` [Qemu-devel] [PULL 1/5] slirp: Allow disabling IPv4 or IPv6 Samuel Thibault
2016-03-31  9:20 ` [Qemu-devel] [PULL 2/5] slirp: Split get_dns_addr Samuel Thibault
2016-03-31  9:20 ` [Qemu-devel] [PULL 3/5] slirp: Add dns6 resolution Samuel Thibault
2016-03-31  9:20 ` [Qemu-devel] [PULL 4/5] slirp: Support link-local DNS addresses Samuel Thibault
2016-03-31  9:20 ` [Qemu-devel] [PULL 5/5] slirp: Add RDNSS advertisement Samuel Thibault
2016-03-31 11:30 ` [Qemu-devel] [PULL 0/5] ipv4-only and ipv6-only support Peter Maydell
2016-03-31 11:44   ` Samuel Thibault
2016-03-31 11:49     ` Vasiliy Tolstov
2016-03-31 11:57       ` Samuel Thibault
2016-03-31 12:03         ` Vasiliy Tolstov
2016-03-31 12:04           ` Vasiliy Tolstov
2016-03-31 12:14             ` Samuel Thibault
2016-03-31 12:20               ` Vasiliy Tolstov
2016-03-31 12:10           ` Samuel Thibault
2016-03-31 12:20             ` Vasiliy Tolstov
2016-03-31 12:47 ` Peter Maydell
2016-03-31 12:51   ` Samuel Thibault
2016-03-31 14:11     ` Peter Maydell
2016-03-31 14:19       ` Samuel Thibault
2016-03-31 14:44         ` Peter Maydell
2016-03-31 14:49           ` Samuel Thibault [this message]

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=20160331144941.GT2636@var.bordeaux.inria.fr \
    --to=samuel.thibault@gnu.org \
    --cc=jan.kiszka@siemens.com \
    --cc=peter.maydell@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).