Additional clid str changes for nfs4 recovery directory

1. Need to skip bad entry in v4recov/v4old to avoid infinite loop.
2. Need to closedir after processing the subdir.

Signed-off-by: Rong Zeng <rongzeng@us.ibm.com>
Log level changed.

If id to name mapping fails,
then log debug message instead of critical error

Signed-off-by: suhrud <supatank@in.ibm.com>
GPFSFSAL_UP_Thread needs to save errno for later use.

Signed-off-by: Rong Zeng <rongzeng@us.ibm.com>
Reduce the severity of the msg related to 'cache missed'
when the export list cache was access the very first time.

Signed-off-by: Rong Zeng <rongzeng@us.ibm.com>
Including tirpc fixes.
1. Fix mem leak when running I/O with kerberos
2. Reject gss request when ticket expires

Signed-off-by: Rong Zeng <rongzeng@us.ibm.com>
Added handling of EUNATCH from GPFS

Signed-off-by: Venkateswararao Jujjuri (JV) <jvrao@linux.vnet.ibm.com>
Signed-off-by: Rong Zeng <rongzeng@us.ibm.com>
cache_inode_rename needs to avoid deadlock.

Signed-off-by: Rong Zeng <rongzeng@us.ibm.com>
avoid delete stale entry's state twice in nfs4_op_open.

Signed-off-by: Rong Zeng <rongzeng@us.ibm.com>
PTHREAD_RWLOCK_UNLOCK macro fix.

Signed-off-by: Rong Zeng <rongzeng@us.ibm.com>
GPFSFSAL_symlink needs to ensure link type upon create.
Otherwise return EXIST.

Signed-off-by: Rong Zeng <rongzeng@us.ibm.com>
Make sure to create the recovery dirs also during grace.
This will make sure that if the first FS fails and there
are no recovery dirs, then they will be created whenever
any node enters grace

Signed-off-by: Poornima Gupte <poornima.gupte@in.ibm.com>
Removed log message for EAGAIN and EBUSY conversion.

Signed-off-by: Srikrishan Malik <srimalik@in.ibm.com>
Trim unreleased free memory in glibc every 1 minute.

If ganesha RSS is greater than 40% total system mem
or freemem is less than 10% of total, trim.

Signed-off-by: Rong Zeng <rongzeng@us.ibm.com>
close file in nfs_Remove for NFSv3 to avoid open but deleted files.

Signed-off-by: Rong Zeng <rongzeng@us.ibm.com>
cache_inode_lookup should not trust cache when icreate is active.

This is exposed with a very slow FSAL create, just after file object
created but before the entry is added to cache. Client's retry create
will fail with EXIST and then lookup will fail due to parent's not
yet invalidated.

A refcnt is added to cache entry and inc before any create happens
and dec after it's added to dentry cache. trust_negative_cache should
evaluate this counter.

Signed-off-by: Rong Zeng <rongzeng@us.ibm.com>