diff options
| author | Shehjar Tikoo <shehjart@gluster.com> | 2010-08-31 06:50:28 +0000 |
|---|---|---|
| committer | Vijay Bellur <vijay@dev.gluster.com> | 2010-08-31 07:44:21 -0700 |
| commit | 217fb3e2acbb221668ad5d54ef4067a2bac47c4a (patch) | |
| tree | 0509f4e58839d6af059c5aaf4279e3454fb4f83a /xlators/nfs/server/src/nfs3-fh.c | |
| parent | e1422d796fefd6a3ae599507e71efdb922eede02 (diff) | |
nfs3: Unref dir fd once usage ends in hard fh resolution
There are three conditions when a dir fd_t needs to be unrefed
when:
a. the inode being searched is found as the candidate entry,
b. we have exhausted all the entries in the current dir,
c. we decide to step into a child directory because of a hash
match.
This decision is made in nfs3_fh_resolve_check_response.
Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
BUG: 1397 (Cached dir fd_ts are a leakin')
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1397
Diffstat (limited to 'xlators/nfs/server/src/nfs3-fh.c')
0 files changed, 0 insertions, 0 deletions