On Mar 29, 2014, at 15:49, Trond Myklebust <trond.myklebust@xxxxxxxxxxxxxxx> wrote: > > On Mar 29, 2014, at 15:34, J. Bruce Fields <bfields@xxxxxxxxxxxx> wrote: > >> On Sat, Mar 29, 2014 at 02:43:39PM -0400, Trond Myklebust wrote: >>> RFC5661 obsoletes NFS4ERR_RESTOREFH in favour of NFS4ERR_NOFILEHANDLE. >> >> Looks right. Any objection to just making this nfserr_restorefh in the >> 4.0 case as well? Hard to imagine how that could cause a 4.0 client any >> problem. > > You mean make both cases return nfserr_nofilehandle (as per RFC5661), right? So, I agree that most clients should handle that, but the problem is that RFC3530bis does not allow it. Either way, this is not a performance critical issue. Any time we get into this situation, it is because the client is utterly screwed up in the first place. The NFS4ERR_STALE_STATEID is the critical one that really needs to be applied... _________________________________ Trond Myklebust Linux NFS client maintainer, PrimaryData trond.myklebust@xxxxxxxxxxxxxxx -- 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
