Re: [PATCH v2] lockd: get rid of reference-counted NSM RPC clients

2015-10-08 Thread J. Bruce Fields
On Wed, Oct 07, 2015 at 05:45:15PM -0400, Trond Myklebust wrote: > On Wed, Oct 7, 2015 at 7:39 AM, Andrey Ryabinin > wrote: > > Currently we have reference-counted per-net NSM RPC client > > which created on the first monitor request and destroyed > > after the last unmonitor request. It's

Re: [PATCH v2] lockd: get rid of reference-counted NSM RPC clients

2015-10-08 Thread J. Bruce Fields
On Wed, Oct 07, 2015 at 05:45:15PM -0400, Trond Myklebust wrote: > On Wed, Oct 7, 2015 at 7:39 AM, Andrey Ryabinin > wrote: > > Currently we have reference-counted per-net NSM RPC client > > which created on the first monitor request and destroyed > > after the last

Re: [PATCH v2] lockd: get rid of reference-counted NSM RPC clients

2015-10-07 Thread Trond Myklebust
On Wed, Oct 7, 2015 at 7:39 AM, Andrey Ryabinin wrote: > Currently we have reference-counted per-net NSM RPC client > which created on the first monitor request and destroyed > after the last unmonitor request. It's needed because > RPC client need to know 'utsname()->nodename', but utsname() >

Re: [PATCH v2] lockd: get rid of reference-counted NSM RPC clients

2015-10-07 Thread J. Bruce Fields
On Wed, Oct 07, 2015 at 02:39:55PM +0300, Andrey Ryabinin wrote: > Currently we have reference-counted per-net NSM RPC client > which created on the first monitor request and destroyed > after the last unmonitor request. It's needed because > RPC client need to know 'utsname()->nodename', but

[PATCH v2] lockd: get rid of reference-counted NSM RPC clients

2015-10-07 Thread Andrey Ryabinin
Currently we have reference-counted per-net NSM RPC client which created on the first monitor request and destroyed after the last unmonitor request. It's needed because RPC client need to know 'utsname()->nodename', but utsname() might be NULL when nsm_unmonitor() called. So instead of holding

Re: [PATCH v2] lockd: get rid of reference-counted NSM RPC clients

2015-10-07 Thread J. Bruce Fields
On Wed, Oct 07, 2015 at 02:39:55PM +0300, Andrey Ryabinin wrote: > Currently we have reference-counted per-net NSM RPC client > which created on the first monitor request and destroyed > after the last unmonitor request. It's needed because > RPC client need to know 'utsname()->nodename', but

Re: [PATCH v2] lockd: get rid of reference-counted NSM RPC clients

2015-10-07 Thread Trond Myklebust
On Wed, Oct 7, 2015 at 7:39 AM, Andrey Ryabinin wrote: > Currently we have reference-counted per-net NSM RPC client > which created on the first monitor request and destroyed > after the last unmonitor request. It's needed because > RPC client need to know

[PATCH v2] lockd: get rid of reference-counted NSM RPC clients

2015-10-07 Thread Andrey Ryabinin
Currently we have reference-counted per-net NSM RPC client which created on the first monitor request and destroyed after the last unmonitor request. It's needed because RPC client need to know 'utsname()->nodename', but utsname() might be NULL when nsm_unmonitor() called. So instead of holding