lockd: stop abusing file_lock_list
Subsystems (4)
RFC PATCH 1/1 lockd: stop abusing file_lock_list
Currently lockd directly access the file_lock_list from fs/locks.c. It does so to mark locks granted or reclaimable. This is very suboptimal, because a) lockd needs to poke into locks.c internals, and
b) it needs to iterate over all locks in the system for marking locks granted or reclaimable.
This patch adds lists for granted and reclaimable locks to the nlm_host structure instead, and adds locks to those.
nlmclnt_lock:
now adds the lock to h_granted instead of setting the NFS_LCK_GRANTED, still O(1)
nlmclnt_mark_reclaim:
goes away completely, replaced by a list_splice_init. Complexity reduced from O(locks in the system) to O(1)
reclaimer:
iterates over h_reclaim now, complexity reduced from O(locks in the system) to O(locks per nlm_host)
fs/lockd/clntlock.c +9 -45
@@ -140,34 +140,6 @@*/ /* -* Mark the locks for reclaiming. -* FIXME: In 2.5 we don't want to iterate through any global file_lock_list. -* Maintain NLM lock reclaiming lists in the nlm_host instead. -*/ -static -void nlmclnt_mark_reclaim (struct nlm_host *host) -{ -struct file_lock *fl; -struct inode *inode; -struct list_head *tmp; - -list_for_each (tmp, &file_lock_list) { - fl = list_entry(tmp, struct file_lock, fl_link); - - inode = fl->fl_file->f_dentry->d_inode; -if (inode->i_sb->s_magic !=NFS_SUPER_MAGIC ) -continue ; -if (fl->fl_u.nfs_fl.owner ==NULL ) -continue ; -if (fl->fl_u.nfs_fl.owner->host != host) -continue ; -if (!(fl->fl_u.nfs_fl.flags &NFS_LCK_GRANTED )) -continue ; - fl->fl_u.nfs_fl.flags |=NFS_LCK_RECLAIM ; - } -} - -/* * Someone has sent us an SM_NOTIFY. Ensure we bind to the new port number, * that we mark locks for reclaiming, and that we bump the pseudo NSM state. */
@@ -179,7 +151,12 @@ host->h_state++; host->h_nextrebind =0 ;nlm_rebind_host (host); -nlmclnt_mark_reclaim (host); + +/* +* Mark the locks for reclaiming. +*/ +list_splice_init (&host->h_granted, &host->h_reclaim); +dprintk ("NLM: reclaiming locks for host %s" , host->h_name); }
@@ -208,9 +185,7 @@ {struct nlm_host *host = (struct nlm_host *) ptr;struct nlm_wait *block; -struct list_head *tmp; -struct file_lock *fl; -struct inode *inode; +struct file_lock *fl, *next;daemonize ("%s-reclaim" , host->h_name);allow_signal (SIGKILL );
@@ -222,20 +197,9 @@/* First, reclaim all locks that have been marked. */ restart: -list_for_each (tmp, &file_lock_list) { - fl = list_entry(tmp, struct file_lock, fl_link); - - inode = fl->fl_file->f_dentry->d_inode; -if (inode->i_sb->s_magic !=NFS_SUPER_MAGIC ) -continue ; -if (fl->fl_u.nfs_fl.owner ==NULL ) -continue ; -if (fl->fl_u.nfs_fl.owner->host != host) -continue ; -if (!(fl->fl_u.nfs_fl.flags &NFS_LCK_RECLAIM )) -continue ; +list_for_each_entry_safe (fl, next, &host->h_reclaim, fl_u.nfs_fl.list) { +list_del (&fl->fl_u.nfs_fl.list); - fl->fl_u.nfs_fl.flags &= ~NFS_LCK_RECLAIM ;nlmclnt_reclaim (host, fl);if (signalled ())break ;
fs/lockd/clntproc.c +6 -5
@@ -504,7 +504,6 @@ {BUG_ON (fl->fl_ops !=NULL ); fl->fl_u.nfs_fl.state =0 ; - fl->fl_u.nfs_fl.flags =0 ; fl->fl_u.nfs_fl.owner =nlm_find_lockowner (host, fl->fl_owner); fl->fl_ops = &nlmclnt_lock_ops; }
@@ -591,8 +590,8 @@if (resp->status ==NLM_LCK_GRANTED ) { fl->fl_u.nfs_fl.state = host->h_state; - fl->fl_u.nfs_fl.flags |=NFS_LCK_GRANTED ; fl->fl_flags |=FL_SLEEP ; +list_add_tail (&fl->fl_u.nfs_fl.list, &host->h_granted);do_vfs_lock (fl); } status =nlm_stat_to_errno (resp->status);
@@ -658,9 +657,11 @@struct nlm_res *resp = &req->a_res;int status; -/* Clean the GRANTED flag now so the lock doesn't get -* reclaimed while we're stuck in the unlock call. */ - fl->fl_u.nfs_fl.flags &= ~NFS_LCK_GRANTED ; +/* +* Remove from the granted list now so the lock doesn't get +* reclaimed while we're stuck in the unlock call. +*/ +list_del (&fl->fl_u.nfs_fl.list);if (req->a_flags &RPC_TASK_ASYNC ) { status = nlmclnt_async_call(req, NLMPROC_UNLOCK,
fs/lockd/host.c +2 -0
@@ -123,6 +123,8 @@ nlm_hosts[hash] = host;INIT_LIST_HEAD (&host->h_lockowners);spin_lock_init (&host->h_lock); +INIT_LIST_HEAD (&host->h_granted); +INIT_LIST_HEAD (&host->h_reclaim);if (++nrhosts >NLM_HOST_MAX ) next_gc =0 ;
include/linux/lockd/lockd.h +2 -0
@@ -58,6 +58,8 @@unsigned long h_expires;/* eligible for GC */ struct list_head h_lockowners;/* Lockowners for the client */ spinlock_t h_lock; +struct list_head h_granted;/* Locks in GRANTED state */ +struct list_head h_reclaim;/* Locks in RECLAIM state */ };/*
include/linux/nfs_fs_i.h +1 -7
@@ -12,8 +12,8 @@*/ struct nfs_lock_info {u32 state; -u32 flags;struct nlm_lockowner *owner; +struct list_head list; };struct nfs4_lock_state ;
@@ -21,10 +21,4 @@ struct nfs4_lock_state *owner; }; -/* -* Lock flag values -*/ -#define NFS_LCK_GRANTED 0x0001/* lock has been granted */ -#define NFS_LCK_RECLAIM 0x0002/* lock marked for reclaiming */ -#endif
fs/locks.c +1 -4
@@ -139,10 +139,7 @@#define for_each_lock (inode, lockp) \ for (lockp = &inode->i_flock; *lockp != NULL; lockp = &(*lockp)->fl_next) -LIST_HEAD (file_lock_list); - -EXPORT_SYMBOL (file_lock_list); - +static LIST_HEAD (file_lock_list);static LIST_HEAD (blocked_list);static kmem_cache_t *filelock_cache;
include/linux/fs.h +0 -2
@@ -730,8 +730,6 @@#define OFFT_OFFSET_MAX INT_LIMIT(off_t)#endif -extern struct list_head file_lock_list; -#include <linux/fcntl.h> extern int fcntl_getlk (struct file *,struct flock __user *);
Quoted 8 lines · Christoph Hellwig
Currently lockd directly access the
file_lock_listfromfs/locks.c. It does so to mark locks granted or reclaimable. This is very suboptimal, because a) lockd needs to poke intolocks.cinternals, and
b) it needs to iterate over all locks in the system for marking locks granted or reclaimable.This patch adds lists for granted and reclaimable locks to the
nlm_hoststructure instead, and adds locks to those.
Thanks! From a quick eyeballing of the code, it looks good.
I'll put it into the NFS_ALL stream for testing (and farm it out to Andrew if all goes well).
Cheers
Trond
Quoted 7 lines · Trond Myklebust
Quoted 6 lines · Christoph Hellwig
Currently lockd directly access the
file_lock_listfromfs/locks.c. It does so to mark locks granted or reclaimable. This is very suboptimal, because a) lockd needs to poke intolocks.cinternals, and
b) it needs to iterate over all locks in the system for marking locks granted or reclaimable.
Quoted 7 lines
Quoted 2 lines
This patch adds lists for granted and reclaimable locks to the
nlm_hoststructure instead, and adds locks to those.Thanks! From a quick eyeballing of the code, it looks good.
I'll put it into the
NFS_ALLstream for testing (and farm it out to Andrew if all goes well).
OK... After testing, it appears it will Oops without the attached patch.
Cheers,
Trond
Author: Trond Myklebust <[email protected]>
lockd: Fix Oopses due to list manipulation errors.
The patch "stop abusing file_lock_list introduces a couple of bugs since the locks may be copied and need to be removed from the lists when they are destroyed.
---
fs/lockd/clntproc.c | 9 ++++++++- 1 files changed, 8 insertions(+), 1 deletions(-)
fs/lockd/clntproc.c +8 -1
@@ -447,12 +447,17 @@ static void nlmclnt_locks_copy_lock(stru {memcpy (&new->fl_u.nfs_fl, &fl->fl_u.nfs_fl,sizeof (new->fl_u.nfs_fl));nlm_get_lockowner (new->fl_u.nfs_fl.owner); +INIT_LIST_HEAD (&new->fl_u.nfs_fl.list); +if (!list_empty (&fl->fl_u.nfs_fl.list)) +list_add (&new->fl_u.nfs_fl.list, &fl->fl_u.nfs_fl.list); }static void nlmclnt_locks_release_private (struct file_lock *fl) {nlm_put_lockowner (fl->fl_u.nfs_fl.owner); fl->fl_ops =NULL ; +if (!list_empty (&fl->fl_u.nfs_fl.list)) +list_del (&fl->fl_u.nfs_fl.list); }static struct file_lock_operations nlmclnt_lock_ops = {
@@ -465,6 +470,7 @@ static void nlmclnt_locks_init_private(sBUG_ON (fl->fl_ops !=NULL ); fl->fl_u.nfs_fl.state =0 ; fl->fl_u.nfs_fl.owner =nlm_find_lockowner (host, fl->fl_owner); +INIT_LIST_HEAD (&fl->fl_u.nfs_fl.list); fl->fl_ops = &nlmclnt_lock_ops; }
@@ -621,7 +627,8 @@ nlmclnt_unlock(struct nlm_rqst *req, str* Remove from the granted list now so the lock doesn't get * reclaimed while we're stuck in the unlock call. */ -list_del (&fl->fl_u.nfs_fl.list); +if (!list_empty (&fl->fl_u.nfs_fl.list)) +list_del_init (&fl->fl_u.nfs_fl.list);if (req->a_flags &RPC_TASK_ASYNC ) { status = nlmclnt_async_call(req, NLMPROC_UNLOCK,
fs/lockd/clntproc.c static void nlmclnt_locks_copy_lock(stru · line 461
Quoted 7 lines · Trond Myklebust
static void
nlmclnt_locks_release_private(struct file_lock *fl){fs/lockd/clntproc.c +2
-0nlm_put_lockowner (fl->fl_u.nfs_fl.owner); fl->fl_ops =NULL ; +if (!list_empty (&fl->fl_u.nfs_fl.list)) +list_del (&fl->fl_u.nfs_fl.list); }
This looks fishy, if invoked twice both will return !list_empty() - list_del_init()?
Why not just always use list_del_init(), if you have to add these checks anyways? A double list_del_init() doesn't cause any harm.
Signature · 1 line
Jens Axboe
Quoted 12 lines · Jens Axboe
fs/lockd/clntproc.c static void nlmclnt_locks_copy_lock(stru · line 461
Quoted 7 lines · Trond Myklebust
static void
nlmclnt_locks_release_private(struct file_lock *fl){fs/lockd/clntproc.c +2
-0nlm_put_lockowner (fl->fl_u.nfs_fl.owner); fl->fl_ops =NULL ; +if (!list_empty (&fl->fl_u.nfs_fl.list)) +list_del (&fl->fl_u.nfs_fl.list); }This looks fishy, if invoked twice both will return !list_empty() -
list_del_init()?
Quoted 2 lines
Why not just always use
list_del_init(), if you have to add these checks anyways? A doublelist_del_init()doesn't cause any harm.
True, but calling the above twice would be a nasty bug anyway: it is the destructor for the private area of the lock.
Cheers,
Trond
Quoted 18 lines · Trond Myklebust
Author: Trond Myklebust <[email protected]>
lockd: Fix Oopses due to list manipulation errors.The patch "stop abusing
file_lock_listintroduces a couple of bugs since the locks may be copied and need to be removed from the lists when they are destroyed.Signed-off-by Trond Myklebust <[email protected]>---
fs/lockd/clntproc.c | 9 ++++++++- 1 files changed, 8 insertions(+), 1 deletions(-)fs/lockd/clntproc.c +0
-0
fs/lockd/clntproc.c static void nlmclnt_locks_copy_lock(stru · line 452
Quoted 6 lines
fs/lockd/clntproc.c +3
-0@@ -447,12 +447,17 @@ static void nlmclnt_locks_copy_lock(stru {memcpy (&new->fl_u.nfs_fl, &fl->fl_u.nfs_fl,sizeof (new->fl_u.nfs_fl));nlm_get_lockowner (new->fl_u.nfs_fl.owner); +INIT_LIST_HEAD (&new->fl_u.nfs_fl.list); +if (!list_empty (&fl->fl_u.nfs_fl.list)) +list_add (&new->fl_u.nfs_fl.list, &fl->fl_u.nfs_fl.list);
list_add initializes �nough so we don't need the INIT_LIST_HEAD in that case, so this could become:
if (list_empty(&fl->fl_u.nfs_fl.list)) INIT_LIST_HEAD(&new->fl_u.nfs_fl.list); else list_add(&new->fl_u.nfs_fl.list, &fl->fl_u.nfs_fl.list);
fs/lockd/clntproc.c nlmclnt_unlock(struct nlm_rqst *req, str · line 631
Quoted 6 lines
fs/lockd/clntproc.c +2
-1* Remove from the granted list now so the lock doesn't get * reclaimed while we're stuck in the unlock call. */ -list_del (&fl->fl_u.nfs_fl.list); +if (!list_empty (&fl->fl_u.nfs_fl.list)) +list_del_init (&fl->fl_u.nfs_fl.list);
Probably should be just unconditionaly. list_del_init isn't a whole lot of instructions, but we save a branch and have more readable code.
While we're at it, don't we need a INIT_LIST_HEAD in nlmclnt_locks_init_private aswell?
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 29 lines · Christoph Hellwig
Quoted 18 lines · Trond Myklebust
Author: Trond Myklebust <[email protected]>
lockd: Fix Oopses due to list manipulation errors.The patch "stop abusing
file_lock_listintroduces a couple of bugs since the locks may be copied and need to be removed from the lists when they are destroyed.Signed-off-by Trond Myklebust <[email protected]>---
fs/lockd/clntproc.c | 9 ++++++++- 1 files changed, 8 insertions(+), 1 deletions(-)fs/lockd/clntproc.c +0
-0fs/lockd/clntproc.c static void nlmclnt_locks_copy_lock(stru · line 452
Quoted 6 lines
fs/lockd/clntproc.c +3
-0@@ -447,12 +447,17 @@ static void nlmclnt_locks_copy_lock(stru {memcpy (&new->fl_u.nfs_fl, &fl->fl_u.nfs_fl,sizeof (new->fl_u.nfs_fl));nlm_get_lockowner (new->fl_u.nfs_fl.owner); +INIT_LIST_HEAD (&new->fl_u.nfs_fl.list); +if (!list_empty (&fl->fl_u.nfs_fl.list)) +list_add (&new->fl_u.nfs_fl.list, &fl->fl_u.nfs_fl.list);
list_addinitializes nough so we don't need theINIT_LIST_HEADin that case, so this could become:
Quoted 4 lines
if (list_empty(&fl->fl_u.nfs_fl.list)) INIT_LIST_HEAD(&new->fl_u.nfs_fl.list); else list_add(&new->fl_u.nfs_fl.list, &fl->fl_u.nfs_fl.list);
Sure.
Quoted 9 lines
fs/lockd/clntproc.c nlmclnt_unlock(struct nlm_rqst *req, str · line 631
Quoted 6 lines
fs/lockd/clntproc.c +2
-1* Remove from the granted list now so the lock doesn't get * reclaimed while we're stuck in the unlock call. */ -list_del (&fl->fl_u.nfs_fl.list); +if (!list_empty (&fl->fl_u.nfs_fl.list)) +list_del_init (&fl->fl_u.nfs_fl.list);Probably should be just unconditionaly.
list_del_initisn't a whole lot of instructions, but we save a branch and have more readable code.
True.
Quoted 2 lines
While we're at it, don't we need a
INIT_LIST_HEADinnlmclnt_locks_init_privateaswell?
Yes. The patch does include one, I believe.
Cheers,
Trond