Re: [Nfs-ganesha-devel] Ganesha stuck in release_openstate().

2017-11-29 Thread Frank Filz
I think that will be resolved by:

https://review.gerrithub.io/#/c/386676/

I'm not sure what kept it from being merged into V2.6-dev.18, but it should
be going into V2.6-dev.19.

Frank

> -Original Message-
> From: Pradeep [mailto:pradeeptho...@gmail.com]
> Sent: Wednesday, November 29, 2017 3:24 PM
> To: nfs-ganesha-devel 
> Subject: [Nfs-ganesha-devel] Ganesha stuck in release_openstate().
> 
> Hello all,
> 
> I'm seeing a case with 2.6-dev12 where 'state' is in owner's state_list
> (nfs4_owner->so_state_list). But it is not in the ht_state_id hash table.
This
> will cause state_del_locked() to return without cleaning up state. Because
of
> this release_openstate() goes into an infinite loop (the errcnt is never
> incremented). Also since we hold 'clientid->cid_mutex' before calling
> release_openstate(), all new mounts are hung as well.
> 
> Any thoughts on how ganesha ends up having 'open state' in nfs4_owner-
> >so_state_list and not in ht_state_id?
> 
> Thanks,
> Pradeep
> 
>

--
> Check out the vibrant tech community on one of the world's most engaging
> tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Nfs-ganesha-devel mailing list
> Nfs-ganesha-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel


[Nfs-ganesha-devel] Ganesha stuck in release_openstate().

2017-11-29 Thread Pradeep
Hello all,

I'm seeing a case with 2.6-dev12 where 'state' is in owner's
state_list (nfs4_owner->so_state_list). But it is not in the
ht_state_id hash table. This will cause state_del_locked() to return
without cleaning up state. Because of this release_openstate() goes
into an infinite loop (the errcnt is never incremented). Also since we
hold 'clientid->cid_mutex' before calling release_openstate(), all new
mounts are hung as well.

Any thoughts on how ganesha ends up having 'open state' in
nfs4_owner->so_state_list and not in ht_state_id?

Thanks,
Pradeep

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel