qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@gnu.org>
To: Vasiliy Tolstov <v.tolstov@selfip.ru>
Cc: libvir-list@redhat.com, QEMU <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] ipv6 slirp network
Date: Mon, 21 Jul 2014 16:51:19 +0200	[thread overview]
Message-ID: <20140721145119.GB5390@type.bordeaux.inria.fr> (raw)
In-Reply-To: <20140721144709.GA5390@type.bordeaux.inria.fr>

[-- Attachment #1: Type: text/plain, Size: 870 bytes --]

Samuel Thibault, le Mon 21 Jul 2014 16:47:09 +0200, a écrit :
> Samuel Thibault, le Mon 21 Jul 2014 16:29:34 +0200, a écrit :
> > Vasiliy Tolstov, le Mon 21 Jul 2014 18:19:17 +0400, a écrit :
> > > 2014-07-21 16:06 GMT+04:00 Samuel Thibault <samuel.thibault@gnu.org>:
> > > > I have pushed it to http://dept-info.labri.fr/~thibault/qemu-ipv6 , in
> > > > the tosubmit branch.
> > > 
> > > 
> > > Inside packer (i'm try to build some centos 7 boxes) i have errors
> > > Qemu stderr: qemu-system-x86_64: slirp/tcp_input.c:1543: tcp_mss:
> > > Assertion `0' failed.
> > 
> > Uh?!  Does the switch statement properly have both AF_INET and AF_INET6
> > cases?
> > 
> > A gdb backtrace would also be useful.
> 
> Mmm, I guess this is coming through tcp_connect().  Could you try the
> attached patch?

Sorry, I should have tested the build before sending, here it is.

Samuel

[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 334 bytes --]

diff --git a/slirp/tcp_subr.c b/slirp/tcp_subr.c
index a1f060b..7fa6173 100644
--- a/slirp/tcp_subr.c
+++ b/slirp/tcp_subr.c
@@ -439,6 +439,7 @@ void tcp_connect(struct socket *inso)
             return;
         }
         so->lhost = inso->lhost;
+        so->so_ffamily = inso->so_ffamily;
     }
 
     tcp_mss(sototcpcb(so), 0);

      reply	other threads:[~2014-07-21 14:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-21 11:34 [Qemu-devel] ipv6 slirp network Vasiliy Tolstov
2014-07-21 11:41 ` Samuel Thibault
2014-07-21 11:42   ` Vasiliy Tolstov
2014-07-21 11:49     ` Samuel Thibault
2014-07-21 11:55       ` Vasiliy Tolstov
2014-07-21 11:59         ` Vasiliy Tolstov
2014-07-21 12:06           ` Samuel Thibault
2014-07-21 12:10             ` Vasiliy Tolstov
2014-07-21 14:19             ` Vasiliy Tolstov
2014-07-21 14:29               ` Samuel Thibault
2014-07-21 14:36                 ` Vasiliy Tolstov
2014-07-21 14:47                 ` Vasiliy Tolstov
2014-07-21 14:52                   ` Samuel Thibault
2014-07-21 19:22                     ` Vasiliy Tolstov
2014-07-21 19:49                       ` Samuel Thibault
2014-07-21 20:12                         ` Vasiliy Tolstov
2014-07-21 20:13                           ` Samuel Thibault
2014-07-21 20:19                             ` Vasiliy Tolstov
2014-07-21 20:30                               ` Samuel Thibault
2014-07-21 20:49                                 ` Samuel Thibault
2014-07-22 10:54                                   ` Vasiliy Tolstov
2014-07-21 14:47                 ` Samuel Thibault
2014-07-21 14:51                   ` 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=20140721145119.GB5390@type.bordeaux.inria.fr \
    --to=samuel.thibault@gnu.org \
    --cc=libvir-list@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=v.tolstov@selfip.ru \
    /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).