[Nfs-ganesha-devel] Re: SAL does not call FSAL for conflicting lock op
For a non-blocking lock, the client will retry it, so no upcall is
necessary or desired from the FSAL.
Daniel
On Tue, Jun 26, 2018 at 1:07 PM, <ntvietvn(a)gmail.com> wrote:
> Hello,
>
> After reading the func state_status_t state_lock, it seems that if ganesha receives a
non-blocking lock overlapping an existing lock, the SAL handles it self by returning
STATE_LOCK_CONFLICT. I also made a test and the result is consistent. Is it normal
behavior and if it is, the FSAL is never called, how do you suggest to test upcall fct of
the FSAL when it grants a waiting lock?
>
> Thank you
> Viet
> _______________________________________________
> Devel mailing list -- devel(a)lists.nfs-ganesha.org
> To unsubscribe send an email to devel-leave(a)lists.nfs-ganesha.org