id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	uname	nginx_version
210	ownership of shared memory zones should be tracked better	Ruslan Ermilov	somebody	"nginx doesn't allow the same shared memory zone to be used for different purposes.
It implements this by assigning zone an ""owner"" tag (an address of the module structure).

It's also a property of the shared memory zone that it survives a reconfiguration.

If a shared memory zone changes ownership, e.g. as a result of reconfiguration, nginx doesn't notice this and may crash, like shown below.

configuration A:
{{{
http {
    limit_conn_zone $binary_remote_addr zone=X:10m;
}
}}}

configuration B:
{{{
http {
    limit_req_zone $binary_remote_addr zone=X:10m rate=1r/s;
}
}}}
"	defect	closed	minor		nginx-core	1.3.x	fixed				nginx/1.3.6