Bug 446715

Description of problem:
Two programs.  One a simple client selecting on a file descriptor for writing,
and the other a simple server that accepts new connections but never reads the
socket.  When the socket opened as socket(AF_INET, SOCK_STREAM, IPPROTO_TCP),
the select in the client correctly shows the socket unavailable for writing once
the write window is full.  However, when the socket is opened as socket(
AF_INET, SOCK_STREAM, IPPROTO_SCTP), then the select always reports that the
socket is available for writing.  (This occurs regardless of whether the socket
was blocking or non-blocking.)

Version-Release number of selected component (if applicable):
lksctp-tools-1.0.6-1.el5.1


How reproducible:
Every time.

Steps to Reproduce:
1. Open server stream, sctp socket and accept new connections, but never read
from the connection.
2. Open client, stream, sctp socket (either blocking or non-blocking) and do
select on write of fd, then write if able.
3. select will always report socket as writable.
  
Actual results:
Select will always report socket as writable (with sctp), works with tcp.

Expected results:
When the send window is closed, the socket is not writable and the file
descriptor should not be included in the writable fd_set.

Additional info: