linux-toradex.git/net/sunrpc/xprtsock.c, branch v2.6.30.8

SUNRPC: Fix the problem of EADDRNOTAVAIL syslog floods on reconnect

2009-05-02T23:35:08+00:00

See http://bugzilla.kernel.org/show_bug.cgi?id=13034

If the port gets into a TIME_WAIT state, then we cannot reconnect without
binding to a new port.

Tested-by: Petr Vandrovec 
Tested-by: Jean Delvare 
Signed-off-by: Trond Myklebust 
Signed-off-by: Linus Torvalds

Merge branch 'devel' into for-linus

2009-04-01T17:28:15+00:00

Merge branch 'master' of /home/davem/src/GIT/linux-2.6/

2009-03-26T22:23:24+00:00

Conflicts:
	drivers/net/wimax/i2400m/usb-notif.c

SUNRPC: Ensure we close the socket on EPIPE errors too...

2009-03-19T19:17:36+00:00

As long as one task is holding the socket lock, then calls to
xprt_force_disconnect(xprt) will not succeed in shutting down the socket.
In particular, this would mean that a server initiated shutdown will not
succeed until the lock is relinquished.
In order to avoid the deadlock, we should ensure that xs_tcp_send_request()
closes the socket on EPIPE errors too.

Signed-off-by: Trond Myklebust

SUNRPC: xs_tcp_connect_worker{4,6}: merge common code

2009-03-19T19:17:35+00:00

Signed-off-by: Trond Myklebust

SUNRPC: Add a sysctl to control the duration of the socket linger timeout

2009-03-19T19:17:34+00:00

Signed-off-by: Trond Myklebust

SUNRPC: Add the equivalent of the linger and linger2 timeouts to RPC sockets

2009-03-19T19:17:34+00:00

This fixes a regression against FreeBSD servers as reported by Tomas
Kasparek. Apparently when using RPC over a TCP socket, the FreeBSD servers
don't ever react to the client closing the socket, and so commit
e06799f958bf7f9f8fae15f0c6f519953fb0257c (SUNRPC: Use shutdown() instead of
close() when disconnecting a TCP socket) causes the setup to hang forever
whenever the client attempts to close and then reconnect.

We break the deadlock by adding a 'linger2' style timeout to the socket,
after which, the client will abort the connection using a TCP 'RST'.

The default timeout is set to 15 seconds. A subsequent patch will put it
under user control by means of a systctl.

Signed-off-by: Trond Myklebust

SUNRPC: Ensure that xs_nospace return values are propagated

2009-03-11T18:38:01+00:00

If xs_nospace() finds that the socket has disconnected, it attempts to
return ENOTCONN, however that value is then squashed by the callers.

Signed-off-by: Trond Myklebust

SUNRPC: Delay, then retry on connection errors.

2009-03-11T18:38:01+00:00

Enforce the comment in xs_tcp_connect_worker4/xs_tcp_connect_worker6 that
we should delay, then retry on certain connection errors.

Signed-off-by: Trond Myklebust

SUNRPC: Return EAGAIN instead of ENOTCONN when waking up xprt->pending

2009-03-11T18:38:00+00:00

While we should definitely return socket errors to the task that is
currently trying to send data, there is no need to propagate the same error
to all the other tasks on xprt->pending. Doing so actually slows down
recovery, since it causes more than one tasks to attempt socket recovery.

Signed-off-by: Trond Myklebust