public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: john slee <indigoid@higherplane.net>
To: Radu Greab <radu@netsoft.ro>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bug report: select on unconnected sockets
Date: Sun, 1 Apr 2001 02:15:24 +1000	[thread overview]
Message-ID: <20010401021524.A28831@higherplane.net> (raw)
In-Reply-To: <15045.64340.14915.404305@ix.netsoft.ro>
In-Reply-To: <15045.64340.14915.404305@ix.netsoft.ro>; from radu@netsoft.ro on Sat, Mar 31, 2001 at 06:44:20PM +0300

On Sat, Mar 31, 2001 at 06:44:20PM +0300, Radu Greab wrote:
> Sorry if this is already known: on a RH 7.0 system with kernel 2.4.2
> or 2.4.3, a select on an unconnected socket incorrectly says that the
> socket is ready for input and output. Of course, reading from the socket
> file descriptor returns -1 and errno is set to ENOTCONN as shown in
> the strace output:
> 
> socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 3
> select(4, [3], [3], [3], {0, 0})        = 2 (in [3], out [3], left {0, 0})
> read(3, 0xbffff668, 1024)               = -1 ENOTCONN (Transport endpoint is not connected)
> 
> I attached a small example program to reproduce the bug.

bleah.  which one is supposed to be right?

linux 2.4
---------
$ uname -a
Linux XXXXX 2.4.2-ac20 #8 Wed Mar 14 01:53:05 EST 2001 i686 unknown
$ ./t
select result=2
read: Transport endpoint is not connected

linux 2.2
---------
$ uname -a
Linux XXXXX 2.2.18 #1 Thu Dec 21 21:13:10 EST 2000 i586 unknown
$ ./t
select result=1

solaris
-------
$ uname -a
SunOS XXXXX 5.7 Generic_106541-07 sun4m sparc sun4m
$ ./t
select result=0

-- 
"Bobby, jiggle Grandpa's rat so it looks alive, please" -- gary larson

  reply	other threads:[~2001-03-31 16:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-31 15:44 bug report: select on unconnected sockets Radu Greab
2001-03-31 16:15 ` john slee [this message]
2001-03-31 16:26   ` Radu Greab

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=20010401021524.A28831@higherplane.net \
    --to=indigoid@higherplane.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=radu@netsoft.ro \
    /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