Welcome! Log In Create A New Profile

Advanced

Re: [PATCH] Avoid memory leak on failure to allocate name during resolving

Roman Arutyunyan
June 19, 2017 07:34AM
Hello Bart,

On Mon, Jun 19, 2017 at 08:00:37AM +0200, Bart Warmerdam wrote:
>
> # HG changeset patch
> # User Bart Warmerdam <bartw@xs4all.nl>
> # Date 1497851445 -7200
> # Mon Jun 19 07:50:45 2017 +0200
> # Branch memleak_resolve_name
> # Node ID dd8c5ef0483cf0abe6f9f88b4bb9ba681aec7be4
> # Parent d1816a2696de8c2faa1cd913a151e5f62a8620f3
> Avoid leak on error allocating name
>
> diff -r d1816a2696de -r dd8c5ef0483c src/core/ngx_resolver.c
> --- a/src/core/ngx_resolver.c Fri Jun 16 18:15:58 2017 +0300
> +++ b/src/core/ngx_resolver.c Mon Jun 19 07:50:45 2017 +0200
> @@ -443,7 +443,7 @@
>
> name.data = ngx_resolver_alloc(r, name.len);
> if (name.data == NULL) {
> - return NGX_ERROR;
> + goto resolve_error;
> }
>
> if (slen == ctx->service.len) {
> @@ -481,6 +481,7 @@
> ngx_resolver_free(r, ctx->event);
> }
>
> +resolve_error:
> ngx_resolver_free(r, ctx);
>
> return NGX_ERROR;

Thanks!

Committed with minor changes.

--
Roman Arutyunyan
_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel
Subject Author Views Posted

[PATCH] Avoid memory leak on failure to allocate name during resolving

Bart Warmerdam 610 June 19, 2017 02:02AM

Re: [PATCH] Avoid memory leak on failure to allocate name during resolving

Roman Arutyunyan 232 June 19, 2017 07:34AM



Sorry, you do not have permission to post/reply in this forum.

Online Users

Guests: 82
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready