From: Samuel Thibault <samuel.thibault@gnu.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"John Snow" <jsnow@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Kamil Rytarowski" <kamil@netbsd.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Kevin Wolf" <kwolf@redhat.com>, "Cleber Rosa" <crosa@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: Python 2 and test/vm/netbsd
Date: Tue, 22 Oct 2019 15:10:52 +0200 [thread overview]
Message-ID: <20191022131052.vswq6xkesofx4p3v@function> (raw)
In-Reply-To: <20191018160019.he52tpvjqolzgswg@function>
Samuel Thibault, le ven. 18 oct. 2019 18:00:19 +0200, a ecrit:
> Philippe Mathieu-Daudé, le ven. 18 oct. 2019 16:58:00 +0200, a ecrit:
> > On 10/18/19 4:29 PM, Eduardo Habkost wrote:
> > > In addition to that, the connect() error should be generating a
> > > ICMP6_UNREACH message, and I'd expect the NetBSD guest to notice
> > > it instead of waiting for timeout.
> >
> > Is this missing in SLiRP?
>
> It was implemented at the time of introduction of IPv6 in SLIRP. Perhaps
> NetBSD has a slightly different behavior which makes the implementation
> fail to notice the error.
It definitely is there in tcp_input(): on tcp_fconnect() error an
ICMP6_UNREACH message is sent. I can confirm that this works with a
Linux host and Linux guest.
Samuel
prev parent reply other threads:[~2019-10-22 13:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 3:00 Python 2 and test/vm/netbsd (was Re: [Qemu-devel] [PULL 0/8] Python queue, 2019-06-07) Eduardo Habkost
2019-10-16 6:11 ` Python 2 and test/vm/netbsd Thomas Huth
2019-10-16 8:25 ` Kamil Rytarowski
2019-10-16 10:59 ` Alex Bennée
2019-10-16 11:02 ` Thomas Huth
2019-10-16 12:23 ` Philippe Mathieu-Daudé
2019-10-16 22:41 ` Eduardo Habkost
2019-10-17 22:05 ` Eduardo Habkost
2019-10-17 22:55 ` Eduardo Habkost
2019-10-18 7:13 ` Thomas Huth
2019-10-18 14:51 ` Eduardo Habkost
2019-10-18 10:44 ` Gerd Hoffmann
2019-10-18 14:29 ` Eduardo Habkost
2019-10-18 14:58 ` Philippe Mathieu-Daudé
2019-10-18 16:00 ` Samuel Thibault
2019-10-18 16:41 ` Eduardo Habkost
2019-10-22 13:16 ` Samuel Thibault
2019-10-22 13:05 ` Kamil Rytarowski
2019-10-22 13:10 ` 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=20191022131052.vswq6xkesofx4p3v@function \
--to=samuel.thibault@gnu.org \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=fam@euphon.net \
--cc=jsnow@redhat.com \
--cc=kamil@netbsd.org \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.