Description of problem: valgrind enabled for nfs process for 3.2.6qa1 release, then executed iozone, untar of linux tar ball, after test completion found these problems, ==20350== 42 bytes in 1 blocks are definitely lost in loss record 7 of 227 ==20350== at 0x4A04A28: calloc (vg_replace_malloc.c:467) ==20350== by 0x4C5C312: __gf_calloc (mem-pool.c:142) ==20350== by 0x7BCC1A9: gf_strdup (mem-pool.h:129) ==20350== by 0x7BCC682: nfs_loc_fill (nfs-common.c:218) ==20350== by 0x7BCC7F5: nfs_inode_loc_fill (nfs-common.c:261) ==20350== by 0x7BCC899: nfs_gfid_loc_fill (nfs-common.c:290) ==20350== by 0x7BCC8EF: nfs_root_loc_fill (nfs-common.c:305) ==20350== by 0x7BF6ED9: nfs3_fh_resolve_root (nfs3-helpers.c:3110) ==20350== by 0x7BF700C: nfs3_fh_resolve_and_resume (nfs3-helpers.c:3146) ==20350== by 0x7BEB921: nfs3_fsinfo (nfs3.c:4593) ==20350== by 0x7BEBA71: nfs3svc_fsinfo (nfs3.c:4627) ==20350== by 0x7BFF25B: nfs_rpcsvc_handle_rpc_call (rpcsvc.c:2018) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: