Since the state_owner_t is referenced in the state_t, this should just fall out of Frank's state rework patches, shouldn't it? Just implement the *2() versions of the FSAL API calls, and you will get a state with each relevant call.
Dan On Mon, Aug 31, 2015 at 2:34 AM, Soumya Koduri <[email protected]> wrote: > Hi, > > As discussed over #ganesha, we are wondering if we can provide any > identifier unique to each NFS client to FSAL so that it may/can help the > backend filesystems to validate the reclaim lock requests. > > The use-case is to allow reclaim/replay of the lock requests by NFS > clients after NFS-Ganesha server reboot or failover (particularly if in > case the backend filesytem hasn't flushed the earlier locks by then). > > The unique identifier may be (assuming they remain same across the NFS > servers in a cluster) - > NLM caller name > NFSv4 client identifier > > Request to share your inputs/comments. > > Thanks, > Soumya > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Nfs-ganesha-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel >
------------------------------------------------------------------------------
_______________________________________________ Nfs-ganesha-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
