Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of prvs=083691ffa1=micha@lenk.info
 designates 188.40.85.232 as permitted sender)
Message-ID: <51855153.6070805@lenk.info>
Date: Sat, 04 May 2013 20:20:03 +0200
From: Micha Lenk <micha@lenk.info>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:10.0.12) Gecko/20130116 Icedove/10.0.12
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Re: mod_proxy seg faulting ?
References: 
 <CAPV0b05_SGch7pxGMcaZjnRp-M-_mkg7-1Tv8JNW6isndmh0sQ@mail.gmail.com>
 <201305031409.43050.sf@sfritsch.de>
In-Reply-To: <201305031409.43050.sf@sfritsch.de>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit

Hi Stefan,

Am 03.05.2013 14:09, schrieb Stefan Fritsch:
> On Thursday 02 May 2013, Thomas Eckert wrote:
>> > Lately, I've been seeing httpd/mod_proxy seg faulting in reverse
>> > proxy setups, frequency increasing.
> 
> I am pretty sure that this is a thread-unsafe pool usage. 
> create_proxy_config() puts the global config pool into 
> (proxy_server_conf)->pool. It is later (during request processing) 
> used all over the place without further locking. This must be a sub-
> pool instead, and it must be protected with a mutex. Or new sub-pools 
> must be created wherever conf->pool is used.

Can you please elaborate the problem of thread-unsafe pool usage a bit
more so that we can better understand why this is causing a segmentation
fault? Or alternatively, do you have any pointer to documentation,
mailinglists, what ever, where to read more about it?

Thanks in advance,
Micha