On 09/27/2016 06:26 PM, Malahal Naineni wrote:
> I did find an issue with merging locks. Please see if a fix around this
> area in ganltc repo, branch "ibm2.3" would fix your issue or not. It was
> reviewed by Frank a while ago but I didn't apply to the upstream stable
> v2.3 yet.
>
Thanks Malahal. yes. I think its below commit -
commit a27663e3346019ddcd9e169182d66714ddb55890
Author: Malahal Naineni <mala...@us.ibm.com>
Date: Thu Jun 2 12:19:50 2016 -0500
Fix checking for existence of prior locks.
It does fix the issue which we have seen. Any particular reason why it
was not considered for V2.3 branch?
Thanks,
Soumya
> Regards, Malahal.
>
>
> On Sep 27, 2016 6:14 PM, "Soumya Koduri" <skod...@redhat.com
> <mailto:skod...@redhat.com>> wrote:
>
> Hi,
>
> We observed a ref leak of cache-inode entry (in V2.3-stable
> codepath) in case if there are multiple locks issued on that entry
> which may get merged. Attached the fix for it.
>
> Kindly review and merge it into V2.3-stable branch.
>
> Thanks,
> Soumya
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Nfs-ganesha-devel mailing list
> Nfs-ganesha-devel@lists.sourceforge.net
> <mailto:Nfs-ganesha-devel@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
> <https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel>
>
>
------------------------------------------------------------------------------
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
