| commit | eb2099f31b0f090684a64ef8df44a30ff7c45fc2 | [log] [tgz] |
|---|---|---|
| author | J. Bruce Fields <bfields@redhat.com> | Sun Apr 07 13:28:16 2013 -0400 |
| committer | J. Bruce Fields <bfields@redhat.com> | Tue Apr 09 09:08:56 2013 -0400 |
| tree | c413f56772a69937303a3b0f6a2e8ee039fa6e14 | |
| parent | bbc9c36c31fc5827c22359a8b0ba9dd71b5eecfc [diff] |
nfsd4: release lockowners on last unlock in 4.1 case In the 4.1 case we're supposed to release lockowners as soon as they're no longer used. It would probably be more efficient to reference count them, but that's slightly fiddly due to the need to have callbacks from locks.c to take into account lock merging and splitting. For most cases just scanning the inode's lock list on unlock for matching locks will be sufficient. Signed-off-by: J. Bruce Fields <bfields@redhat.com>