| commit | 566709bd627caf933ab8edffaf598203a0c5c8b2 | [log] [tgz] |
|---|---|---|
| author | Jeff Layton <jlayton@primarydata.com> | Mon Aug 11 14:09:35 2014 -0400 |
| committer | Jeff Layton <jlayton@primarydata.com> | Mon Aug 11 14:24:22 2014 -0400 |
| tree | 5a9b57da3e5b11e827d25dc2b95ff1b36a6701cb | |
| parent | 8144f1f69943f447fd1bcb2d26ca011002d5df63 [diff] |
locks: don't call locks_release_private from locks_copy_lock All callers of locks_copy_lock pass in a brand new file_lock struct, so there's no need to call locks_release_private on it. Replace that with a warning that fires in the event that we receive a target lock that doesn't look like it's properly initialized. Acked-by: J. Bruce Fields <bfields@fieldses.org> Signed-off-by: Jeff Layton <jlayton@primarydata.com>