Likely shouldn't be using cmd->temp_pool in configuration code.

Copterfly / modwsgi

Automatically exported from code.google.com/p/modwsgi

0 stars 0 forks source link

Likely shouldn't be using cmd->temp_pool in configuration code. #108

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

Parts of code dealing with configuration are using cmd->temp_pool. This pool 
though is deleted 
prior to any requests being handled in Apache child worker processes, possibly 
also in daemon 
processes, but not sure.

If references are retained to memory from this pool for information, possible 
that the memory could 
be modified by something else later on and corrupt it.

Best to change all use of cmd->temp_pool to cmd->pool.

Note, haven't see this cause an issue yet, but being cautious all the same.

Original issue reported on code.google.com by Graham.Dumpleton@gmail.com on 13 Sep 2008 at 12:17

GoogleCodeExporter commented 8 years ago

Already fixed in subversion trunk for version 3.0 at revision r1070.

Original comment by Graham.Dumpleton@gmail.com on 18 Sep 2008 at 3:51

Changed state: Started
Added labels: Milestone-Release3.0

GoogleCodeExporter commented 8 years ago

This relates to http://code.google.com/p/modwsgi/issues/detail?id=108 as well.

This was backported in 2.X branch for 2.4 in revision r1129.

Original comment by Graham.Dumpleton@gmail.com on 16 Mar 2009 at 10:29

Added labels: Milestone-Release2.4
Removed labels: Milestone-Release3.0

GoogleCodeExporter commented 8 years ago

Related issue is actually http://code.google.com/p/modwsgi/issues/detail?id=78.

Original comment by Graham.Dumpleton@gmail.com on 19 Mar 2009 at 9:50

GoogleCodeExporter commented 8 years ago

Version 2.4 of mod_wsgi now released.

Original comment by Graham.Dumpleton@gmail.com on 11 Apr 2009 at 10:25

Changed state: Fixed