When I removed the mylease callback for the 2.6.38 merge window, I screwed up: I forgot that nfsd could hold multiple leases on the same file on behalf of multiple clients, and that all those leases would be associated with the same file descriptor. This could cause a problem when removing a lease, as the wrong lease could get removed. There's no real reason why we should hold multiple leases; we can instead just keep one lease, and use a count of the number of delegations to decide when to remove it. The following patches do that (after a little preperatory cleanup). We could instead revert the mylease removal. But I think this is still a small enough change to justify after the merge window. So barring objections I intend to to submit this for 2.6.38 soon (along with a couple other bugfixes I have queued up.) --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
