Skip to content
This repository was archived by the owner on May 29, 2023. It is now read-only.

Conversation

@cuber
Copy link
Contributor

@cuber cuber commented May 14, 2019

  1. because life cycle of cmcf is as long as the nginx worker, so updating this variable dynamically will case potential memory access overflow risk
    see the discussion A crash bugfix for ngx_http_dyups_module alibaba/tengine#1133

  2. completely test for the modules below
    tengine/ngx_http_upstream_check_module
    tengine/ngx_http_upstream_consistent_hash_module

  3. seperate unit test cases files for different module

@cuber cuber force-pushed the bugfix/potential_memory_overflow branch from 019b7f0 to 11f0aa1 Compare May 14, 2019 07:17
completely test for `tengine/ngx_http_upstream_check_module` and `tengine/ngx_http_upstream_consistent_hash_module`
seperate unit test cases files for different module
@cuber cuber force-pushed the bugfix/potential_memory_overflow branch from 11f0aa1 to 85ed958 Compare May 14, 2019 07:20
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant