From: Taimoor <taimoor.mrza@gmail.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Taimoor Mirza <tmirza@codesourcery.com>
Subject: [Qemu-devel] [PATCH v3] slirp: Port redirection option behave differently on Linux and Windows
Date: Fri, 16 Aug 2013 00:25:35 +0500 [thread overview]
Message-ID: <1376594735-7433-1-git-send-email-tmirza@codesourcery.com> (raw)
From: Taimoor Mirza <tmirza@codesourcery.com>
port redirection code uses SO_REUSEADDR socket option before binding to
host port. Behavior of SO_REUSEADDR is different on Windows and Linux.
Relaunching QEMU with same host and guest port redirection values on Linux
throws error but on Windows it does not throw any error.
Problem is discussed in http://lists.gnu.org/archive/html/qemu-devel/2013-04/msg03089.html
Signed-off-by: Taimoor Mirza <tmirza@codesourcery.com>
---
Changes in v3:
- Removed extra commit
Changes in v2:
- Changed #ifdef to #ifndef as SO_REUSEADDR should not be set in case of Windows.
slirp/socket.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/slirp/socket.c b/slirp/socket.c
index 8e8819c..25d60e7 100644
--- a/slirp/socket.c
+++ b/slirp/socket.c
@@ -627,7 +627,9 @@ tcp_listen(Slirp *slirp, uint32_t haddr, u_int hport, uint32_t laddr,
addr.sin_port = hport;
if (((s = qemu_socket(AF_INET,SOCK_STREAM,0)) < 0) ||
+#ifndef _WIN32
(qemu_setsockopt(s, SOL_SOCKET, SO_REUSEADDR, &opt, sizeof(int)) < 0) ||
+#endif
(bind(s,(struct sockaddr *)&addr, sizeof(addr)) < 0) ||
(listen(s,1) < 0)) {
int tmperrno = errno; /* Don't clobber the real reason we failed */
--
1.7.5.4
next reply other threads:[~2013-08-15 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 19:25 Taimoor [this message]
2013-08-30 11:04 ` [Qemu-devel] [PATCH v3] slirp: Port redirection option behave differently on Linux and Windows Jan Kiszka
2013-09-01 15:46 ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
2013-09-01 16:13 ` Stefan Weil
2013-09-02 1:36 ` Mirza, Taimoor
2013-09-02 6:18 ` Jan Kiszka
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=1376594735-7433-1-git-send-email-tmirza@codesourcery.com \
--to=taimoor.mrza@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=tmirza@codesourcery.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 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).