apr_xlate not thread safe

[Sander Striker <st...@apache.org>]

Bringing this up here for obvious reasons...

http://subversion.tigris.org/issues/show_bug.cgi?id=974

"Attempting to use mod_dav_svn with Apache's worker MPM has revealed
 that the UTF8 conversions are not thread safe.
 
   http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=24986
 
 The conclusion is that Subversion stores an apr_xlate_t object in the
 global pool (well two really, one from UTF8 the other to UTF8) that
 gets shared by all the threads. The apr_xlate_t object itself stores a
 pool, so this pool is then shared by all the threads. Pools are not
 meant to be shared by threads without locking, so this doesn't work."

Sander

RE: apr_xlate not thread safe

[Bill Stoddard <bi...@wstoddard.com>]

> --On Friday, November 8, 2002 4:46 AM +0100 Sander Striker 
> <st...@apache.org> wrote:
> 
> > Bringing this up here for obvious reasons...
> >
> > http://subversion.tigris.org/issues/show_bug.cgi?id=974
> >
> > "Attempting to use mod_dav_svn with Apache's worker MPM has revealed
> >  that the UTF8 conversions are not thread safe.
> 
> Nah, Subversion's use of the apr_xlate is not thread-safe.
> 
> Patch submitted to Subversion mailing list to fix this.  -- justin
> 

This type of bug is going to bite us over and over.

Bill

Re: apr_xlate not thread safe

[Justin Erenkrantz <je...@apache.org>]

--On Friday, November 8, 2002 4:46 AM +0100 Sander Striker 
<st...@apache.org> wrote:

> Bringing this up here for obvious reasons...
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=974
>
> "Attempting to use mod_dav_svn with Apache's worker MPM has revealed
>  that the UTF8 conversions are not thread safe.

Nah, Subversion's use of the apr_xlate is not thread-safe.

Patch submitted to Subversion mailing list to fix this.  -- justin