Move list of fsal obj and ds handles to fsal_module from fsal_export

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Remove unnecessary references to export from fsal_obj_handle

In these cases, we can get the proper export from req_op_context.

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Add struct fsal_export *fsal_export to req_op_context

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Stop referencing fsal_obj_handle export in FSAL_GPFS

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Stop referencing fsal_obj_handle export in FSAL_PT

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Stop referencing fsal_obj_handle export in FSAL_VFS

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Stop referencing fsal_obj_handle export in FSAL_PROXY

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Stop referencing fsal_obj_handle export in FSAL_PSEUDO

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Clean some dead code from FSAL/Stackable_FSALs/FSAL_NULL/nullfs_methods.h

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Stop referencing fsal_obj_handle export in FSAL_GLUSTER

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Stop referencing fsal_obj_handle export in FSAL_LUSTRE

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Stop referencing fsal_obj_handle export in FSAL_ZFS

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Add req_op_context to FSAL share_op

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Remove include fsal_up.h where not used

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Strip unused FSAL_UP calls

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Remove need for FSAL_UP to utilize the export and object belongs to

FSAL_VFS stores up_ops in it's private vfs_fsal_obj_handle. This may not
be ideal, but is a solution.

FSAL_GPFS already has a pointer to the up_ops for each FSAL_UP thread.

notify_device is now passed the exportid. Ultimately exportid will not
be part of device id, at which point presumably the uint64_t exportid
parameter will be renamed, but this step allows us to disassociate
export from fsal_obj_handle.

For FSAL_CEPH we also keep the up_ops in the private handle.

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Provide a generic "root_op_context" with initializer

This provides a standard mechanism for creating a root req_op_context
when an actual req_op_context is not available or not appropriate.

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Add UNKNOWN_REQUEST to use for constructed root req_op_context

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Proper root_op_context, use entry->first_export for cache_inode_destroyer

Now that we have a common initializer replace synthetic_context with
a proper root_op_context.

Instead of relying on the soon to be deprecated obj_handle->export,
use entry->first_export to find the entry's fsal_export.

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Use root_op_context in fsal_up_top.c and fill in proper export

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>