locks: don't call locks_release_private from locks_copy_lock
authorJeff Layton <jlayton@primarydata.com>
Mon, 11 Aug 2014 18:09:35 +0000 (14:09 -0400)
committerJeff Layton <jlayton@primarydata.com>
Mon, 11 Aug 2014 18:24:22 +0000 (14:24 -0400)
commit566709bd627caf933ab8edffaf598203a0c5c8b2
tree5a9b57da3e5b11e827d25dc2b95ff1b36a6701cb
parent8144f1f69943f447fd1bcb2d26ca011002d5df63
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>
fs/locks.c