[MUD-Dev] Re: Sockets permanently in CLOSE_WAIT state. (fwd)

[Oliver Jowett]

This might be of interest to people using threads for socket i/o.

-O

---------- Forwarded message ----------
Date: 20 Aug 1998 23:27:36 +0200
From: Andi Kleen <ak at muc.de>
To: Andy Sloane <andude at guildsoftware.com>
Cc: linux-kernel at vger.rutgers.edu, ak at muc.de
Subject: Re: Sockets permanently in CLOSE_WAIT state.

In article <19980818195423.B1233 at aikon.incarnate.net>,
Andy Sloane <andude at guildsoftware.com> writes:
> --7JfCtLOvnd9MIVvH
> Content-Type: text/plain; charset=us-ascii

> 	Ok, here is the code to "exploit" this.  It works under linux
> 2.0.35; that's all I've tested it on.  Maybe it's already fixed in 2.1.

This is a known 2.0 deficiency, it doesn't do thread locking in net/socket.c.
You may say that sockets are not really thread-safe in 2.0
This is fixed in 2.1, and I can't reproduce it with 2.1.115.

-Andi