On 5/8/19 10:29 AM, Frank Filz wrote:
> Since FSAL_CEPH is just using the pointer to the state_owner_t as
a 64-bit
> integer, it cannot be duplicated. That pointer is unique. You can use the NFS4 or
> NLM owner if you want (it's stored in the state_owner_t). Those are unique,
> because they're based on the client ID, which is guaranteed unique to a client.
>
> In the case of FSAL_CEPH, the pointer will have changed across reboot.
> I'm not sure how it's handling it. Jeff would know more.
To be clear, the NLM lock owner is a client generated opaque string. There is no
guarantee that it is unique across all clients. I'm pretty sure the NFS4 owner is the
same way.
This is true, but our state_owner_t (which is what is passed in) already
has a client ID in it, so the FSAL can just use that to make it unique.
That's what I meant.
Daniel