locks: don't allocate a lock context for an F_UNLCK request
authorJeff Layton <jeff.layton@primarydata.com>
Fri, 3 Apr 2015 13:04:03 +0000 (09:04 -0400)
committerJeff Layton <jeff.layton@primarydata.com>
Fri, 3 Apr 2015 13:04:03 +0000 (09:04 -0400)
commit5c1c669a1b2435e071d566b6db1a8e6b26542ba1
tree512cf17f4056133293b863e38d81097f921037e0
parent663d5af750b8c025d0dfea2cf2a4b4a78cafa3a7
locks: don't allocate a lock context for an F_UNLCK request

In the event that we get an F_UNLCK request on an inode that has no lock
context, there is no reason to allocate one. Change
locks_get_lock_context to take a "type" pointer and avoid allocating a
new context if it's F_UNLCK.

Then, fix the callers to return appropriately if that function returns
NULL.

Signed-off-by: Jeff Layton <jlayton@primarydata.com>
fs/locks.c