]> git.baikalelectronics.ru Git - kernel.git/commit
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)
commitc4f63f84c7bc3bf459fb307e4d37abb66fda57ef
tree5a9b57da3e5b11e827d25dc2b95ff1b36a6701cb
parentd607ed4dfe9eef8a83758296ef648c359897df49
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