| commit | 6b447539aa9aaac0a0215f3e28a0839553210e7e | [log] [tgz] |
|---|---|---|
| author | Trond Myklebust <trond.myklebust@primarydata.com> | Sat Jan 24 18:38:15 2015 -0500 |
| committer | Trond Myklebust <trond.myklebust@primarydata.com> | Sat Jan 24 18:46:46 2015 -0500 |
| tree | 66bfecb6aecbf164a9ab61dcb5ebe639c4d6d43f | |
| parent | 39071e6fff7d7e11a5993afd67240ef04a4d05a0 [diff] |
NFSv4: Always do open_to_lock_owner if the lock stateid is uninitialised The original text in RFC3530 was terribly confusing since it conflated lockowners and lock stateids. RFC3530bis clarifies that you must use open_to_lock_owner when there is no lock state for that file+lockowner combination. Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>