Possible deadlock in named atomic infrastructure used by revprop caching

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 will be deadlocked if *any* of
named atomic shared file contains some invalid data.

-- 
Ivan Zhakov
CTO | VisualSVN | http://www.visualsvn.com