locks: rename lock-manager ops
Both the filesystem and the lock manager can associate operations with a lock. Confusingly, one of them (fl_release_private) actually has the same name in both operation structures. It would save some confusion to give the lock-manager ops different names. Signed-off-by: J. Bruce Fields <bfields@redhat.com>
This commit is contained in:
@@ -632,7 +632,7 @@ nlmsvc_cancel_blocked(struct nlm_file *file, struct nlm_lock *lock)
|
||||
|
||||
/*
|
||||
* This is a callback from the filesystem for VFS file lock requests.
|
||||
* It will be used if fl_grant is defined and the filesystem can not
|
||||
* It will be used if lm_grant is defined and the filesystem can not
|
||||
* respond to the request immediately.
|
||||
* For GETLK request it will copy the reply to the nlm_block.
|
||||
* For SETLK or SETLKW request it will get the local posix lock.
|
||||
@@ -719,9 +719,9 @@ static int nlmsvc_same_owner(struct file_lock *fl1, struct file_lock *fl2)
|
||||
}
|
||||
|
||||
const struct lock_manager_operations nlmsvc_lock_operations = {
|
||||
.fl_compare_owner = nlmsvc_same_owner,
|
||||
.fl_notify = nlmsvc_notify_blocked,
|
||||
.fl_grant = nlmsvc_grant_deferred,
|
||||
.lm_compare_owner = nlmsvc_same_owner,
|
||||
.lm_notify = nlmsvc_notify_blocked,
|
||||
.lm_grant = nlmsvc_grant_deferred,
|
||||
};
|
||||
|
||||
/*
|
||||
|
Reference in New Issue
Block a user