Keep track of all locks per export, not just NLM locks

For unexport purposes, we will need to know all the locks associated
with an export, not just the NLM locks.

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Catch some ERR_FSAL_STALE conditions in SAL and call cache_inode_kill_entry

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Don't count STATE_FSAL_ESTALE and STATE_DEAD_ENTRY as errors in notify and unlock all

These errors indicate the entry was stale/dead, and thus can not have
any state, so it is ok to continue, the state in question has definitely
been released (or will be released as soon as all LRU references on the
entry are released.

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Keep all NLM shares on a list per export.

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Callers to nfs3_FhandleToCache already have the correct export in req_ctx

So we don't need to lookup the export by id.

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
MORE Don't count STATE_FSAL_ESTALE and STATE_DEAD_ENTRY as errors in notify and unlock all

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
MORE Keep all NLM shares on a list per export.

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