On Sun, Aug 25, 2019 at 01:12:34PM +0300, Alex Lyakas wrote: > You are listed as maintainers of nfsd. Can you please take a look at > the below patch? Thanks! I take it this was found by some kind of code analysis or fuzzing, not use in production? Asking because I've been considering just deprecating it, so: > > After we fixed this, we confirmed that the openowner is not freed > > prematurely. It is freed by release_openowner() final call > > to nfs4_put_stateowner(). > > > > However, we still get (other) random crashes and memory corruptions > > when nfsd_inject_forget_client_openowners() and > > nfsd_inject_forget_openowners(). > > According to our analysis, we don't see any other refcount issues. > > Can anybody from the community review these flows for other potentials issues? I'm wondering how much effort we want to put into tracking all that down. --b.
