• J
    lockd: Remove FL_LOCKD flag · 7117bf3d
    J. Bruce Fields 提交于
    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: NJ. Bruce Fields <bfields@citi.umich.edu>
    Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
    7117bf3d
fs.h 65.8 KB