From: Steven Dake <sdake@mvista.com>
To: Alex Riesen <fork0@users.sourceforge.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Nick Palmer <nick@sluggardy.net>,
netdev@oss.sgi.com
Subject: Re: select implementation not POSIX compliant?
Date: Wed, 11 Aug 2004 14:57:29 -0700 [thread overview]
Message-ID: <1092261449.4717.65.camel@persist.az.mvista.com> (raw)
In-Reply-To: <20040811194018.GA3971@steel.home>
You will find poll works as you desire but select does not. I recommend
porting to poll anyway; select sucks bad. You might even try out epoll
in 2.6.
Thanks
Good luck
On Wed, 2004-08-11 at 12:40, Alex Riesen wrote:
> On linux-kernel, Nick Palmer wrote:
> > I am working on porting some software from Solaris to Linux 2.6.7. I
> > have run into a problem with the interaction of select and/or
> > recvmsg and close in our multi-threaded application. The application
> > expects that a close call on a socket that another thread is
> > blocking in select and/or recvmsg on will cause select and/or
> > recvmsg to return with an error. Linux does not seem to do this. (I
> > also verified that the same issue exists in Linux 2.4.25, just to be
> > sure it wasn't introduced in 2.6 in case you were wondering.)
>
> It works always for stream sockets and does not at all (even with
> shutdown, even using poll(2) or read(2) instead of select) for dgram
> sockets.
>
> What domain (inet, local) are your sockets in?
> What type (stream, dgram)?
>
> There will probably be a problem anyway with changing the behaviour:
> there surely is lots of code, which start complaining about select and
> poll finishing "unexpectedly".
>
> I used this to check:
>
> #include <unistd.h>
> #include <stdio.h>
> #include <stdlib.h>
> #include <sys/socket.h>
> #include <sys/wait.h>
> #include <netinet/in.h>
> #include <fcntl.h>
>
> int main(int argc, char* argv[])
> {
> int status;
> int fds[2];
> fd_set set;
> #if 0
> puts("stream");
> if ( socketpair(PF_LOCAL, SOCK_STREAM, 0, fds) < 0 )
> #else
> puts("dgram");
> if ( socketpair(PF_LOCAL, SOCK_DGRAM, 0, fds) < 0 )
> #endif
> {
> perror("socketpair");
> exit(1);
> }
> fcntl(fds[0], F_SETFL, fcntl(fds[0], F_GETFL) | O_NONBLOCK);
> fcntl(fds[1], F_SETFL, fcntl(fds[1], F_GETFL) | O_NONBLOCK);
> switch ( fork() )
> {
> case 0:
> sleep(1);
> close(fds[0]);
> shutdown(fds[1], SHUT_RD);
> close(fds[1]);
> exit(0);
> break;
> case -1:
> perror("fork");
> exit(1);
> }
> close(fds[1]);
> FD_ZERO(&set);
> FD_SET(fds[0], &set);
> select(fds[0] + 1, &set, NULL, NULL, 0);
> wait(&status);
> return 0;
> }
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2004-08-11 21:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 17:00 Nick Palmer
2004-08-11 19:40 ` Alex Riesen
2004-08-11 20:33 ` khandelw
2004-08-11 21:23 ` Alex Riesen
2004-08-13 20:13 ` Nick Palmer
2004-08-11 21:57 ` Steven Dake [this message]
2004-08-13 20:12 ` Nick Palmer
2004-08-11 20:49 Manfred Spraul
2004-08-13 20:18 ` Nick Palmer
2004-08-13 22:05 ` Alan Cox
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=1092261449.4717.65.camel@persist.az.mvista.com \
--to=sdake@mvista.com \
--cc=fork0@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=nick@sluggardy.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
all inboxes | Powered by JetHome®