From: Stefan Fritsch Date: Mon, 8 Jul 2013 20:51:41 +0000 (+0000) Subject: vote, promote X-Git-Tag: 2.4.5~21 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=4fc6685316158a6247464af14981b8e7872fe97b;p=apache vote, promote git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1500940 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/STATUS b/STATUS index e503ec4d1a..3c7caee9cb 100644 --- a/STATUS +++ b/STATUS @@ -91,7 +91,14 @@ RELEASE SHOWSTOPPERS: PATCHES ACCEPTED TO BACKPORT FROM TRUNK: [ start all new proposals below, under PATCHES PROPOSED. ] - + * mod_proxy: Fix pool usage by protecting w/ a mutex + trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1480627 + http://svn.apache.org/viewvc?view=revision&revision=1482859 + http://svn.apache.org/viewvc?view=revision&revision=1483190 + http://svn.apache.org/viewvc?view=revision&revision=1484343 + http://svn.apache.org/viewvc?view=revision&revision=1500437 + 2.4.x patch: trunk works, modulo CHANGES + +1: jim, minfrin, sf PATCHES PROPOSED TO BACKPORT FROM TRUNK: [ New proposals should be added at the end of the list ] @@ -119,29 +126,6 @@ PATCHES PROPOSED TO BACKPORT FROM TRUNK: -0.5: sf: I would prefer if this sat in trunk for a few months first to receive more testing. - * mod_proxy: Fix pool usage by protecting w/ a mutex - trunk patch: http://svn.apache.org/viewvc?view=revision&revision=1480627 - http://svn.apache.org/viewvc?view=revision&revision=1482859 - http://svn.apache.org/viewvc?view=revision&revision=1483190 - http://svn.apache.org/viewvc?view=revision&revision=1484343 - http://svn.apache.org/viewvc?view=revision&revision=1500437 - 2.4.x patch: trunk works, modulo CHANGES - +1: jim, minfrin - sf says: - - ap_proxy_sync_balancer() seems to use conf->pool in several - places, but only one place is protected by conf->mutex. - I don't think this is correct. - Also, I can't find any place where conf->mutex is initialized. - jj says: - - conf->pool is used in 2 places, both are now protected - sf says: - - ap_proxy_initialize_worker() is called from proxy_handler() with - conf->pool. I guess this should also be mutex protected? - jj says: - - it is: ap_proxy_initialize_worker() uses the mutex internally. - (line ~1735) - - * mod_proxy_http: Make the proxy-interim-response environment variable effective by formally overriding origin server behaviour. trunk patch: http://svn.apache.org/r1483027