From: Jeff Layton <jlayton@primarydata.com>
Date: Mon, 11 Aug 2014 18:09:35 +0000 (-0400)
Subject: locks: don't call locks_release_private from locks_copy_lock
X-Git-Tag: omap-for-v3.17/fixes-against-rc2~49^2~4
X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=566709bd627caf933ab8edffaf598203a0c5c8b2;p=pandora-kernel.git

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>
---

Reading git-diff-tree failed