[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Strategy for FSFS locking fix and 1.2

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-04-13 20:36:03 CEST

Greg Hudson <ghudson@MIT.EDU> wrote on 04/12/2005 03:28:15 PM:

> The FSFS locking fix comes in three logical parts:
> (1) Cache the uuid in memory (in FSFS) for technical reasons.
> (2) Add the serialized_init machinery to the FS loader library, and
> use it in the FSFS back end to serialize access to the write
> lock.
> (3) Add the svn_fs_initialize() API and calls to it. If it is not
> used, libsvn_fs makes a best-effort fallback which (a) leaks a
> little heap memory if the svn libraries are unloaded, and (b)
> could, if one is very unlucky, fail to serialize accesses to the
> write lock.

If only parts 1 and 2 are implemented, does that still "solve" the problem
when the repos is being accessed ONLY by svnserve or mod_dav_svn?



Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 13 20:36:56 2005

This is an archived mail posted to the Subversion Dev mailing list.