From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: [Qemu-devel] [PULL v1 04/11] io: set LISTEN flag explicitly for listen sockets
Date: Thu, 27 Oct 2016 14:57:31 +0200 [thread overview]
Message-ID: <20161027125738.19357-5-berrange@redhat.com> (raw)
In-Reply-To: <20161027125738.19357-1-berrange@redhat.com>
The SO_ACCEPTCONN ioctl is not portable across OS, with
some BSD versions and OS-X not supporting it. There is
no viable alternative to this, so instead just set the
feature explicitly when creating a listener socket.
The current users of qio_channel_socket_new_fd() won't
ever be given a listening socket, so there's no problem
with no auto-detecting it in this scenario
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
---
io/channel-socket.c | 8 +-------
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/io/channel-socket.c b/io/channel-socket.c
index 75cbca3..d7e03f6 100644
--- a/io/channel-socket.c
+++ b/io/channel-socket.c
@@ -72,9 +72,6 @@ qio_channel_socket_set_fd(QIOChannelSocket *sioc,
int fd,
Error **errp)
{
- int val;
- socklen_t len = sizeof(val);
-
if (sioc->fd != -1) {
error_setg(errp, "Socket is already open");
return -1;
@@ -110,10 +107,6 @@ qio_channel_socket_set_fd(QIOChannelSocket *sioc,
qio_channel_set_feature(ioc, QIO_CHANNEL_FEATURE_FD_PASS);
}
#endif /* WIN32 */
- if (getsockopt(fd, SOL_SOCKET, SO_ACCEPTCONN, &val, &len) == 0 && val) {
- QIOChannel *ioc = QIO_CHANNEL(sioc);
- qio_channel_set_feature(ioc, QIO_CHANNEL_FEATURE_LISTEN);
- }
return 0;
@@ -220,6 +213,7 @@ int qio_channel_socket_listen_sync(QIOChannelSocket *ioc,
close(fd);
return -1;
}
+ qio_channel_set_feature(QIO_CHANNEL(ioc), QIO_CHANNEL_FEATURE_LISTEN);
return 0;
}
--
2.9.3
next prev parent reply other threads:[~2016-10-27 12:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 12:57 [Qemu-devel] [PULL v1 00/11] Merge qio 2016/10/27 Daniel P. Berrange
2016-10-27 12:57 ` [Qemu-devel] [PULL v1 01/11] io: Fix double shift usages on QIOChannel features Daniel P. Berrange
2016-10-27 12:57 ` [Qemu-devel] [PULL v1 02/11] io: Use qio_channel_has_feature() where applicable Daniel P. Berrange
2016-10-27 12:57 ` [Qemu-devel] [PULL v1 03/11] io: Introduce a qio_channel_set_feature() helper Daniel P. Berrange
2016-10-27 12:57 ` Daniel P. Berrange [this message]
2016-10-27 12:57 ` [Qemu-devel] [PULL v1 05/11] io: Add a QIOChannelSocket cleanup test Daniel P. Berrange
2016-10-27 12:57 ` [Qemu-devel] [PULL v1 06/11] io: add ability to set a name for IO channels Daniel P. Berrange
2016-10-27 12:57 ` [Qemu-devel] [PULL v1 07/11] nbd: set name for all I/O channels created Daniel P. Berrange
2016-10-27 12:57 ` [Qemu-devel] [PULL v1 08/11] char: " Daniel P. Berrange
2016-10-27 12:57 ` [Qemu-devel] [PULL v1 09/11] migration: " Daniel P. Berrange
2016-10-27 12:57 ` [Qemu-devel] [PULL v1 10/11] vnc: " Daniel P. Berrange
2016-10-27 12:57 ` [Qemu-devel] [PULL v1 11/11] main: set names for main loop sources created Daniel P. Berrange
2016-10-27 15:10 ` [Qemu-devel] [PULL v1 00/11] Merge qio 2016/10/27 Peter Maydell
2016-10-27 15:33 ` Peter Maydell
2016-10-27 21:40 ` Daniel P. Berrange
2016-10-27 21:46 ` Peter Maydell
2016-10-28 15:31 ` Peter Maydell
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=20161027125738.19357-5-berrange@redhat.com \
--to=berrange@redhat.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).