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

Re: Another 1.4 release critical bug

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2006-08-06 06:33:17 CEST

On 8/5/06, Philip Martin <philip@codematters.co.uk> wrote:
> "Garrett Rooney" <rooneg@electricjellyfish.net> writes:
>
> > +/* Global pool to allocate DSOs in. */
> > +static apr_pool_t *dso_pool;
>
> > +void
> > +svn_dso_initialize()
> > +{
> > + if (dso_pool)
> > + return;
> > +
> > + dso_pool = svn_pool_create(NULL);
>
> > +svn_error_t *
> > +svn_dso_load(apr_dso_handle_t **dso, const char *fname)
> > +{
> > + apr_status_t status;
> > +
> > + if (! dso_pool)
> > + svn_dso_initialize();
>
> If we agree on Vlad's refactoring of the atomic_init_once stuff for
> SASL then this might be another place it could be used.

That had occurred to me, but I didn't use it in this patch because I
wanted to keep things fairly self contained for backport purposes.
Once 1.4.x is kicked out the door I'd want to go back and make it use
the atomics code. Of course, we could also backport the atomics code,
but honestly, small changes to 1.4.x seem best at this point, and it's
not like this is the only non-thread-safe initialization code we've
got in the tree.

-garrett

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Aug 6 06:33:43 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.