On Sun, 2008-11-09 at 16:04 -0500, J. Bruce Fields wrote: > I can't see any reason we particularly need to call this until the last > gssd closes the pipe. There's a very good reason: if we call rpc_close_pipes() then it is because the kernel listener is shutting down. At that point, we want to return EPIPE for all future read() or write() attempts by gssd. > Also, this allows to guarantee that open_pipe and release_pipe are > called strictly in pairs; open_pipe on the first open, release_pipe on > the last close. That'll make it very easy for the gss code to keep > track of which pipes gssd is using. ...unless the gss code is no longer running. -- Trond Myklebust Linux NFS client maintainer NetApp Trond.Myklebust@xxxxxxxxxx www.netapp.com -- 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
