Bug in 2.1.119 UNIX sockets

Elliot Lee (sopwith@redhat.com)
Tue, 8 Sep 1998 23:16:46 -0400 (EDT)


This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Send mail to mime@docserver.cac.washington.edu for more info.

---1345349078-1645444558-905311006=:18289
Content-Type: TEXT/PLAIN; charset=US-ASCII

When run on 2.0.33, this program always hangs, because it is trying to
connect to its own socket. This is probably the Right Thing.

When run on 2.1.119, this program completes the run successfully. The
first time, the connect() (on a blocking fd) succeeds even before the
connection is accept()'d. In subsequent runs, the bind to the address
fails with EADDRINUSE, until I manually 'rm -f' the socket file.

Both behaviours (succeeding connect, failing bind) seem erroneous.
Demonstration program attached.

Hope this helps,
-- Elliot
Progress (n.): The process through which Usenet has evolved from smart
people in front of dumb terminals to dumb people in front of smart
terminals. -- obs@burnout.demon.co.uk

---1345349078-1645444558-905311006=:18289
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="t-usock-loop.c"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.LNX.3.96.980908231646.18289B@lacrosse.redhat.com>
Content-Description: Test program

I2luY2x1ZGUgPHN5cy9zb2NrZXQuaD4NCiNpbmNsdWRlIDxzdHJpbmcuaD4N
CiNpbmNsdWRlIDxzeXMvdW4uaD4NCg0KI2lmbmRlZiBTVU5fTEVODQojZGVm
aW5lIFNVTl9MRU4ocHRyKSAoKHNpemVfdCkgKCgoc3RydWN0IHNvY2thZGRy
X3VuICopIDApLT5zdW5fcGF0aCkgICAgICAgICBcDQogICAgICAgICAgICAg
ICAgICAgICAgKyBzdHJsZW4gKChwdHIpLT5zdW5fcGF0aCkpDQojZW5kaWYN
Cg0KaW50IG1haW4odm9pZCkNCnsNCgljaGFyIGJ1ZltdID0gIkhlbGxvIHdv
cmxkLCB0aGlzIGlzIGNvb2whIjsNCglzdHJ1Y3Qgc29ja2FkZHJfdW4gZm9v
LCBiYXI7DQoJaW50IG47DQoJaW50IGZkOw0KCWludCBmZDIsIGNsaWZkOw0K
DQoJZmQgPSBzb2NrZXQoQUZfVU5JWCwgU09DS19TVFJFQU0sIDApOw0KCWZv
by5zdW5fZmFtaWx5ID0gQUZfVU5JWDsNCglzdHJjcHkoZm9vLnN1bl9wYXRo
LCAiL3RtcC9mb28tdXNvY2siKTsNCgliaW5kKGZkLCAmZm9vLCBzaXplb2Yo
Zm9vKSk7DQoJbGlzdGVuKGZkLCAxKTsNCg0KCWJhci5zdW5fZmFtaWx5ID0g
QUZfVU5JWDsNCglzdHJjcHkoYmFyLnN1bl9wYXRoLCAiL3RtcC9mb28tdXNv
Y2siKTsNCgljbGlmZCA9IHNvY2tldChBRl9VTklYLCBTT0NLX1NUUkVBTSwg
MCk7DQoJY29ubmVjdChjbGlmZCwgJmJhciwgU1VOX0xFTigmYmFyKSk7DQoN
CglmZDIgPSBhY2NlcHQoZmQsICZmb28sIHNpemVvZihmb28pKTsNCgluID0g
c2l6ZW9mKGZvbyk7DQoJZ2V0cGVlcm5hbWUoZmQyLCAmZm9vLCAmbik7DQoJ
cHJpbnRmKCIlc1xuIiwgZm9vLnN1bl9wYXRoKTsNCgl3cml0ZShmZDIsIGJ1
Ziwgc2l6ZW9mKGJ1ZikpOw0KCWNsb3NlKGZkMik7DQoJcmV0dXJuIDA7DQp9
DQo=
---1345349078-1645444558-905311006=:18289--

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/faq.html