[Bug 254590] NFSv4.1 mounts from the Linux client gets "stuck" with partially closed TCP connection

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254590

--- Comment #1 from Rick Macklem <rmacklem at FreeBSD.org> ---
Created attachment 223621
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223621&action=edit
add soshutdown() calls to server side krpc for non-functional TCP conn

Jason Breitman reported "stuck" Linux NFSv4.1 mounts
against a FreeBSD NFSv4.1 server.
Although the underlying cause is not known, the
TCP connection is in FIN_WAIT2 on the client
and CLOSE_WAIT on the server.

The server side TCP remains in CLOSE_WAIT because
the server's krpc cannot soclose() the socket until
the backchannel is re-assigned to another TCP connection.
This re-assignment happens when the client establishes
a new TCP connection and does a BindConnectionToSession
operation on the new connection.

This patch adds soshutdown(SHUT_WR) calls in the 3 places
where the server krpc knows that the TCP socket is no
longer usable.
--> I think this will allow the TCP connection to proceed
    past CLOSE_WAIT and allow the TCP connection closure
    to complete.
This will hopefully get the Linux mount "unstuck".

-- 
You are receiving this mail because:
You are the assignee for the bug.