From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nft PATCH 0/4] Memleak fixes and some minor cleanups
Date: Thu, 24 Aug 2017 19:19:03 +0200 [thread overview]
Message-ID: <20170824171903.GA27332@salvia> (raw)
In-Reply-To: <20170824171413.31737-1-phil@nwl.cc>
On Thu, Aug 24, 2017 at 07:14:09PM +0200, Phil Sutter wrote:
> The following series fixes two sources of memleaks as reported by
> valgrind (see patches 1 and 4). Patches 2 and 3 contain some minor
> cleanups I found while searching for the leaks.
Series applied, thanks.
prev parent reply other threads:[~2017-08-24 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 17:14 [nft PATCH 0/4] Memleak fixes and some minor cleanups Phil Sutter
2017-08-24 17:14 ` [nft PATCH 1/4] scanner: Fix for memleak due to unclosed file pointer Phil Sutter
2017-08-24 17:14 ` [nft PATCH 2/4] scanner: Fix for wrong parameter type of scanner_destroy() Phil Sutter
2017-08-24 17:14 ` [nft PATCH 3/4] scanner: Make use of yylex_init_extra() Phil Sutter
2017-08-24 17:14 ` [nft PATCH 4/4] parser: Fix for memleak when commands fail Phil Sutter
2017-08-24 17:19 ` 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=20170824171903.GA27332@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
/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).