From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Eric Jallot <ejallot@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft] src: obj: fix memleak in parser_bison.y
Date: Wed, 9 Oct 2019 12:17:09 +0200 [thread overview]
Message-ID: <20191009101709.e322s2rdilzizexf@salvia> (raw)
In-Reply-To: <20191008134724.17839-1-ejallot@gmail.com>
On Tue, Oct 08, 2019 at 03:47:24PM +0200, Eric Jallot wrote:
> Each object (secmark, synproxy, quota, limit, counter) is dynamically allocated
> by the parser and not freed at exit.
> However, there is no need to use dynamic allocation here because struct obj
> already provides the required storage. Update the grammar to ensure that
> obj_alloc() is called before config occurs.
Applied.
prev parent reply other threads:[~2019-10-09 10:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 13:47 [PATCH nft] src: obj: fix memleak in parser_bison.y Eric Jallot
2019-10-09 10:17 ` Pablo Neira Ayuso [this message]
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=20191009101709.e322s2rdilzizexf@salvia \
--to=pablo@netfilter.org \
--cc=ejallot@gmail.com \
--cc=netfilter-devel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).