From: "Álvaro Neira Ayuso" <alvaroneay@gmail.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [libnftnl PATCH v2] ruleset: fix a leak when we use the set lists
Date: Fri, 13 Feb 2015 17:04:09 +0100 [thread overview]
Message-ID: <54DE2079.6010901@gmail.com> (raw)
In-Reply-To: <20150213155728.GA6287@salvia>
El 13/02/15 a las 16:57, Pablo Neira Ayuso escribió:
> On Wed, Feb 11, 2015 at 10:12:22PM +0100, Alvaro Neira Ayuso wrote:
>> ==18632== 285 (16 direct, 269 indirect) bytes in 1 blocks are definitely lost in
>> loss record 6 of 6
>> ==18632== at 0x4C272B8: calloc (vg_replace_malloc.c:566)
>> ==18632== by 0x5043822: nft_set_list_alloc (set.c:977)
>> ==18632== by 0x5045483: nft_ruleset_json_parse (ruleset.c:442)
>> ==18632== by 0x50458BE: nft_ruleset_do_parse (ruleset.c:696)
>> ==18632== by 0x408AEC: do_command (rule.c:1317)
>> ==18632== by 0x406B05: nft_run (main.c:194)
>> ==18632== by 0x40667C: main (main.c:360)
>
> Also applied. I found more leaks, just pushed a patch to fix them
>
I have already seen the changes. Sorry and thanks Pablo to fix them.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-02-13 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 21:12 [libnftnl PATCH v2] rule: don't release the tree parameter in the function nft_jansson_parse_rule Alvaro Neira Ayuso
2015-02-11 21:12 ` [libnftnl PATCH v2] ruleset: fix a leak when we use the set lists Alvaro Neira Ayuso
2015-02-13 15:57 ` Pablo Neira Ayuso
2015-02-13 16:04 ` Álvaro Neira Ayuso [this message]
2015-02-13 15:56 ` [libnftnl PATCH v2] rule: don't release the tree parameter in the function nft_jansson_parse_rule Pablo Neira Ayuso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54DE2079.6010901@gmail.com \
--to=alvaroneay@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.