From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Rostedt Subject: Re: It's back! (Re: [REGRESSION] NFS is creating a hidden port (left over from xs_bind() )) Date: Thu, 30 Jun 2016 16:07:26 -0400 Message-ID: <20160630160726.304a3d14@gandalf.local.home> References: <20160630085950.61e5c7e0@gandalf.local.home> <20160630112341.5ab5a821@gandalf.local.home> <72EF2259-3A78-4FE3-8E0E-B3090FDFF14F@primarydata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Jeff Layton , Eric Dumazet , Schumaker Anna , "Linux NFS Mailing List" , "Linux Network Devel Mailing List" , LKML , "Andrew Morton" , Fields Bruce To: Trond Myklebust Return-path: In-Reply-To: <72EF2259-3A78-4FE3-8E0E-B3090FDFF14F-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org> Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: netdev.vger.kernel.org On Thu, 30 Jun 2016 18:30:42 +0000 Trond Myklebust wrote: > Wait. So the NFS mount is still active, it=E2=80=99s just that the so= cket > disconnected due to no traffic? That should be OK. Granted that the > port can=E2=80=99t be reused by another process, but you really don=E2= =80=99t want > that: what if there are no other ports available and you start > writing to a file on the NFS partition? What would cause the port to be connected to a socket again? I copied a large file to the nfs mount, and the hidden port is still there? Remember, this wasn't always the case, the hidden port is a recent issue. I ran wireshark on this and it appears to create two ports for NFS. One of them is canceled by the client (sends a FIN/ACK) and this port is what lays around never to be used again, and uses the other port for all connections after that. When I unmount the NFS directory, the port is finally freed (but has no socket attached to it). What is the purpose of keeping this port around= ? I can reproduce this by having the client unmount and remount the directory. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html