I finally got around to looking at the delegation self-conflict problem you asked me about: it looks not hard at all to make the server stop revoking delegation in cases it's the client modifiying the file (or metatadata), as long as we're in the 4.1 case or otherwise know which client we're dealing with. I should post patches next week. Remind me how you expect to take advantage of this? I think you wanted to eliminate some cases where the client has to preemptively return delegations, but don't you then need some way to know ahead of time what the server behavior is? --b. -- 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
