Re: Fw: Deadlock regression in v2.6.31.6

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Nov 27, 2009 at 01:07, Stephen R. van den Berg <srb@xxxxxxx> wrote:
> RPC:       worker connecting xprt cfa94400 to address: addr=1.2.3.151
> port=2049 proto=tcp
> RPC:       cfa94400 connect status 99 connected 0 sock state 7

errno 99 means EADDRNOTAVAIL.  In userspace this normally is solved by
using the REUSEADDR sockopt.  In xprtsock.c we try something like:

                /* We're probably in TIME_WAIT. Get rid of existing socket,
                 * and retry
                 */
                set_bit(XPRT_CONNECTION_CLOSE, &xprt->state);
                xprt_force_disconnect(xprt);

I'd guess that this needs to be fixed, or the REUSEADDR sockopt needs to be set.
-- 
Sincerely,
                Stephen R. van den Berg.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux