Re: Possible deadlock in named atomic infrastructure used by revprop caching

2014-08-27 Thread Stefan Fuhrmann
On Wed, Aug 27, 2014 at 6:49 PM, Ivan Zhakov wrote: > On 18 August 2014 16:51, Stefan Fuhrmann > wrote: > > On Tue, Aug 12, 2014 at 7:22 PM, Ivan Zhakov wrote: > >> > >> Stefan, > >> > >> I've noticed another severe issue in named atomic infrastructure used > >> by revprop caching code while re

Re: Possible deadlock in named atomic infrastructure used by revprop caching

2014-08-27 Thread Ivan Zhakov
On 18 August 2014 16:51, Stefan Fuhrmann wrote: > On Tue, Aug 12, 2014 at 7:22 PM, Ivan Zhakov wrote: >> >> Stefan, >> >> I've noticed another severe issue in named atomic infrastructure used >> by revprop caching code while reviewing r1611379 fix: >> svn_atomic_namespace__create() doesn't releas

Re: Possible deadlock in named atomic infrastructure used by revprop caching

2014-08-18 Thread Stefan Fuhrmann
On Tue, Aug 12, 2014 at 7:22 PM, Ivan Zhakov wrote: > Stefan, > > I've noticed another severe issue in named atomic infrastructure used > by revprop caching code while reviewing r1611379 fix: > svn_atomic_namespace__create() doesn't release file lock and > process-wide mutex (!) on error in libsv

Possible deadlock in named atomic infrastructure used by revprop caching

2014-08-12 Thread Ivan Zhakov
Stefan, I've noticed another severe issue in named atomic infrastructure used by revprop caching code while reviewing r1611379 fix: svn_atomic_namespace__create() doesn't release file lock and process-wide mutex (!) on error in libsvn_subr\named_atomic.c:446. Which is basically mean that server w