Reservations which alter default imagemeta values may affect other reservations
-------------------------------------------------------------------------------
Key: VCL-573
URL: https://issues.apache.org/jira/browse/VCL-573
Project: VCL
Issue Type: Bug
Components: vcld (backend)
Affects Versions: 2.2.1
Reporter: Andy Kurth
Assignee: Andy Kurth
Fix For: 2.3
There is a bug involving the hash reference containing the default imagemeta
values. utils.pm::get_default_imagemeta_info will retrieve the default values
from the database and then save a cached copy in $ENV{imagemeta_info}{default}.
This cached hash reference is returned for subsequent calls to
get_default_imagemeta_info. This data is retrieved before vcld forks a process
for each reservation. As a result, multiple reservation processes share the
same hash reference. If one process changes anything in this hash, it affects
other processes.
This is occurring with the checkuser value. This value is being changed to 0
for server requests. Once changed by one reservation, all subsequent
reservations which use the default imagemeta data have the value set to 0.
The code must be updated so that reservations can't affect each other.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
