Remove wcc pre-attrs form Write and Commit Replies

Given that Ganesha need to make multiple calls to underlying filesystem
to perform write and then to get attributes, there is no way we can provide
accurate/atomic wcc pre-attrs. Because of this, the attr times on the client
side are not matching, resulting in invalidating client's cache. Removing
wcc pre-attrs in the Write and Commit replies, allows client to accurately
follow close-to-open semantics and keep the client cache sane.

Signed-off-by: Venkateswararao Jujjuri "<jvrao@linux.vnet.ibm.com>
Wakeup LRU thread only if it is sleeping
Also downgrade the message from Event to Info

Signed-off-by: Venkateswararao Jujjuri "<jvrao@linux.vnet.ibm.com>
Free only allocated xprt private data.

The issue was the non-agreement of gsh_free_xprt_private
and its caller on the type of its argument.

Signed-off-by: Matt Benjamin <matt@linuxbox.com>
Pull in fixes in tirpc for:
1) memory leak
2) lock issues causing memory currption
Add -D directory option to tools/findlog.sh

Signed-off-by: Frank Filz <ffilz@us.ibm.com>
Make generic ACL code and GPFS ACL code same so GPFS can use generic

Signed-off-by: Frank Filz <ffilz@us.ibm.com>
Use generic ACL code for FSAL_PT

Signed-off-by: Frank Filz <ffilz@us.ibm.com>
Introduce COMMON_test_access

Signed-off-by: Frank Filz <ffilz@us.ibm.com>
Remove Use_Test_Access option

Ganesha really depends on doing all permission checking, we will not
defer permission checking to the underlying file system.

Signed-off-by: Frank Filz <ffilz@us.ibm.com>
Strip lots of code and Use COMMON_test_access instead

Signed-off-by: Frank Filz <ffilz@us.ibm.com>
Strip explicit permission checking from FSAL_GPFS

Permission checking will be done uniformly up in Cache_Inode layer.

Signed-off-by: Frank Filz <ffilz@us.ibm.com>
Strip explicit permission checking from FSAL_PT

Permission checking will be done up in cache_inode_setattr

This is the FSAL_PT equivalent of commits:
e202b2344dea80d59220cec64879b31c9216667c
1ea7d624dacfb62d5cc906e0a5973c32dc27f091

Signed-off-by: Frank Filz <ffilz@us.ibm.com>
Strip explicit permission checking from FSALs: HPSS, LUSTRE, POSIX, VFS, XFS

Permission checking will be done uniformly up in Cache_Inode layer.

Signed-off-by: Frank Filz <ffilz@us.ibm.com>
Strip explicit permission checking from MFSL

Permission checking will be done uniformly up in Cache_Inode layer.

Signed-off-by: Frank Filz <ffilz@us.ibm.com>
Strip local op routines from FSAL_TEMPLATE

The routines in FSAL/common_methods.c should be used unless they must be
overode.

Signed-off-by: Frank Filz <ffilz@us.ibm.com>
Strip testing of FSAL_access and FSAL_test_access

Signed-off-by: Frank Filz <ffilz@us.ibm.com>
Strip unused FSAL access check routines

The following routines are no longer used (only FSAL_test_access is still used):

FSAL_access
FSAL_setattr_access
FSAL_rename_access
FSAL_create_access
FSAL_unlink_access
FSAL_link_access

Signed-off-by: Frank Filz <ffilz@us.ibm.com>
MORE Strip unused FSAL access check routines

Signed-off-by: Frank S. Filz <ffilz@us.ibm.com>
Remove unused FSAL_OWNER_OK flag

This flag was originally implemented to allow permission checking to evaluate
the conditions where the file owner is allowed access despite the mode or ACL.
This condition is now evaluated directly for I/O operations.

Signed-off-by: Frank S. Filz <ffilz@us.ibm.com>
Remove unused FSAL_F_OK flag

Signed-off-by: Frank S. Filz <ffilz@us.ibm.com>