summaryrefslogtreecommitdiff
path: root/fs/lockd/svclock.c
diff options
context:
space:
mode:
authorJ. Bruce Fields <bfields@fieldses.org>2006-03-20 21:44:26 +0300
committerTrond Myklebust <Trond.Myklebust@netapp.com>2006-03-20 21:44:26 +0300
commit7117bf3dfb10b534a017260d9fc643bc1d0afd2a (patch)
treea7060dc3d8a5f54c5beb41885620aaf99aac42f9 /fs/lockd/svclock.c
parent8dc7c3115b611c00006eac3ee5b108296432aab7 (diff)
downloadlinux-7117bf3dfb10b534a017260d9fc643bc1d0afd2a.tar.xz
lockd: Remove FL_LOCKD flag
Currently lockd identifies its own locks using the FL_LOCKD flag. This doesn't scale well to multiple lock managers--if we did this in nfsv4 too, for example, we'd be left with only one free flag bit. Instead, we just check whether the file manager ops (fl_lmops) set on this lock are our own. The only use for this is in nlm_traverse_locks, which uses it to find locks that need cleaning up when freeing a host or a file. In the long run it might be nice to do reference counting instead of traversing all the locks like this.... Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'fs/lockd/svclock.c')
-rw-r--r--fs/lockd/svclock.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/fs/lockd/svclock.c b/fs/lockd/svclock.c
index d683dd022e08..d50946dcddd9 100644
--- a/fs/lockd/svclock.c
+++ b/fs/lockd/svclock.c
@@ -313,8 +313,6 @@ nlmsvc_lock(struct svc_rqst *rqstp, struct nlm_file *file,
/* Get existing block (in case client is busy-waiting) */
block = nlmsvc_lookup_block(file, lock, 0);
- lock->fl.fl_flags |= FL_LOCKD;
-
again:
/* Lock file against concurrent access */
down(&file->f_sema);