diff options
author | Trond Myklebust <Trond.Myklebust@netapp.com> | 2007-12-11 22:01:56 -0500 |
---|---|---|
committer | Trond Myklebust <Trond.Myklebust@netapp.com> | 2007-12-11 22:01:56 -0500 |
commit | 5cef338b30c110daf547fb13d99f0c77f2a79fbc (patch) | |
tree | 4608bf1961dfb3f2f50d72d1b3c7a82daf031933 /fs/hugetlbfs/inode.c | |
parent | 4584f520e1f773082ef44ff4f8969a5d992b16ec (diff) |
NFSv2/v3: Fix a memory leak when using -onolock
Neil Brown said:
> Hi Trond,
>
> We found that a machine which made moderately heavy use of
> 'automount' was leaking some nfs data structures - particularly the
> 4K allocated by rpc_alloc_iostats.
> It turns out that this only happens with filesystems with -onolock
> set.
> The problem is that if NFS_MOUNT_NONLM is set, nfs_start_lockd doesn't
> set server->destroy, so when the filesystem is unmounted, the
> ->client_acl is not shutdown, and so several resources are still
> held. Multiple mount/umount cycles will slowly eat away memory
> several pages at a time.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Acked-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'fs/hugetlbfs/inode.c')
0 files changed, 0 insertions, 0 deletions