"bfields@xxxxxxxxxxxx" <bfields@xxxxxxxxxxxx> writes: > I'm just looking for a concise explanation of why your patch is > important. And I probably haven't dug enough, but I'm still not quite > following. > > If I understand right, the only visible change from your patch will be > returning DELEG_REVOKED instead of BAD_STATEID to 4.1 clients in some > cases. I'm not clear what the result was (for old or new clients)--a > client left believing it held a delegation when it didn't, or a client > entering an infinite state manager loop? The current Linux client will "lose" a delegation on DELEGRETURN if it does not see NFS4ERR_DELEG_REVOKED. This is unrecoverable and will result in the client state manager looping unable to satisfy the server's inevitable assertion of SEQ4_STATUS_RECALLABLE_STATE_REVOKED. RFC5661 10.2.1: "A client normally finds out about revocation of a delegation when it uses a stateid associated with a delegation and receives one of the errors NFS4ERR_EXPIRED, NFS4ERR_ADMIN_REVOKED, or NFS4ERR_DELEG_REVOKED." Thanks, Andy -- Andrew W. Elble aweits@xxxxxxxxxxxxxxxxxx Infrastructure Engineer, Communications Technical Lead Rochester Institute of Technology PGP: BFAD 8461 4CCF DC95 DA2C B0EB 965B 082E 863E C912 -- 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
