Properly permission check cache_inode_create

Signed-off-by: Frank Filz <ffilz@us.ibm.com>
NEEDS WORK Improve permission checking in cache_inode_remove

This still needs work because also have to permission
check the file, and check S_ISVTX

Signed-off-by: Frank Filz <ffilz@us.ibm.com>
Improve permission checking in cache_inode_link

Signed-off-by: Frank Filz <ffilz@us.ibm.com>
Strip 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>

Conflicts:

	src/Cache_inode/cache_inode_access.c
Remove 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>
Use COMMON_setattr_access for FSAL_PROXY

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 MFSL_access call

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>
Add allowed and denied parms to fsal_test_access and fsal_check_access

These parms allow access check to return the specific access mask bits
that were allowed and denied if the caller desires.

These will be used by cache inode permission checking to make some
more complex decisions, also, it will allow the protocol ACCESS routines
to make a single access check and be able to identify which bits should
be returned to the client.

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