-
Notifications
You must be signed in to change notification settings - Fork 291
The pool pointer is now available for ngx_http_modsecurity_config_cleanup #87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
It seems that this PR is also reasonable for owasp-modsecurity/ModSecurity#1546 |
@@ -649,7 +650,7 @@ ngx_http_modsecurity_config_cleanup(void *data) | |||
|
|||
dd("deleting a loc conf -- RuleSet is: \"%p\"", t->rules_set); | |||
|
|||
old_pool = ngx_http_modsecurity_pcre_malloc_init(NULL); | |||
old_pool = ngx_http_modsecurity_pcre_malloc_init(t->pool); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Regardless the parameter here I guess the end result will be the same.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh wait, i think i've get your point. let me discuss with @defanator.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
7efd4f0
to
c6ea19d
Compare
@defanator @zimmerle I did a rebase to apply patch more cleanly. |
Merged! Thanks! |
I did a little research and found out that the rules that are initialized in the pool by the
msc_rules_add_file
ormsc_rules_add
can not be freed by themsc_rules_cleanup
becausengx_http_modsecurity_config_cleanup
does not know anything about this pool (since it is NULL).