Zach Brown e803b10bca scoutfs: drop lock refcnt/users under task ref ...

If scoutfs_unlock() sees that it isn't the last task using a lock it
just returns.  It doesn't unlock the lock and it doesn't drop the lock
refcnt and users.

This leaks the lock refcnt and users because find_alloc_scoutfs_lock()
always increments them when it finds a lock.  Inflated counts will stop
the shrinker from freeing the locks and eventually the counts will wrap
and could cause locks to be freed while they're still in use.

We can either always drop the refcnt/users in unlock or we can drop them
in lock as we notice that our task already has the lock.  I chose to
have the task ref hold one refcnt/users which are only dropped as the
final task unlocks.

Signed-off-by: Zach Brown <zab@versity.com>

2018-01-15 10:04:15 -08:00

..

Documentation

Flesh out some pieces of the scoutfs.md doc

2017-04-18 13:51:10 -07:00

src

scoutfs: drop lock refcnt/users under task ref

2018-01-15 10:04:15 -08:00

.gitignore

Change docker container to versity/rpm-build

2017-12-12 11:43:09 -08:00

Makefile

scoutfs: turn on cluster locking stats

2017-11-10 11:44:39 -08:00