From: Samuel Thibault <samuel.thibault@gnu.org>
To: steven@steven676.net
Cc: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] slirp: deliver received TCP RSTs to the guest
Date: Wed, 6 Apr 2016 14:57:43 +0200 [thread overview]
Message-ID: <20160406125743.GC28379@var.bordeaux.inria.fr> (raw)
In-Reply-To: <1c0611a61621b2069df831b48b937fa49cc264bd.1459896208.git.steven@steven676.net> <cover.1459896208.git.steven@steven676.net>
Hello,
Thanks for this!
steven@steven676.net, on Tue 05 Apr 2016 17:13:58 -0700, wrote:
> The second,
> which fixes delivery of an RST interrupting an already-established TCP
> connection, was submitted by Edgar Iglesias in 2008 and appears to have
> been missed then. The last patch fixes the case where the remote end
> sends RST in reply to our SYN (rejects our incoming connection attempt).
It seems I'm getting another crash with these: sowrite would be called
too for the reseted socket, while the socket has been freed and is not
even on the polling list any more, I had to additionally do the patch
below, could you review it so I can push the whole series?
> I've been unable to test the specific case it
> addresses (an established connection interrupted by RST),
It's actually quite easy: just reboot the server :) The new instance of
the server will send a RST whenever the client sends more data.
Samuel
diff --git a/slirp/slirp.c b/slirp/slirp.c
index fef526c..b13b9af 100644
--- a/slirp/slirp.c
+++ b/slirp/slirp.c
@@ -553,6 +553,11 @@ void slirp_pollfds_poll(GArray *pollfds, int select_error)
if (ret > 0) {
tcp_output(sototcpcb(so));
}
+ if (ret < 0) {
+ /* Socket error and thus removed, do not try to do
+ * anything more with it. */
+ continue;
+ }
}
/*
next prev parent reply other threads:[~2016-04-06 12:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 0:13 [Qemu-devel] [PATCH 0/3] slirp: deliver received TCP RSTs to the guest steven
2016-04-06 0:14 ` [Qemu-devel] [PATCH 1/3] slirp: don't crash when tcp_sockclosed() is called with a NULL tp steven
2016-04-06 0:14 ` [Qemu-devel] [PATCH 2/3] slirp: Propagate host TCP RST to the guest steven
2016-04-06 8:28 ` Paolo Bonzini
2016-04-06 8:36 ` Edgar E. Iglesias
2016-04-06 14:59 ` Steven Luo
2016-04-06 0:14 ` [Qemu-devel] [PATCH 3/3] slirp: handle deferred ECONNREFUSED on non-blocking TCP sockets steven
2016-04-06 7:26 ` [Qemu-devel] [PATCH 0/3] slirp: deliver received TCP RSTs to the guest Thomas Huth
2016-04-06 8:40 ` Edgar E. Iglesias
2016-04-06 12:57 ` Samuel Thibault [this message]
2016-04-07 0:00 ` Steven Luo
2016-04-07 0:17 ` Samuel Thibault
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=20160406125743.GC28379@var.bordeaux.inria.fr \
--to=samuel.thibault@gnu.org \
--cc=edgar.iglesias@xilinx.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=steven@steven676.net \
/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).