From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Giuseppe Longo <giuseppelng@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 2/2] nft: mem leak in nft_rule_list_cb
Date: Tue, 25 Jun 2013 12:00:26 +0200 [thread overview]
Message-ID: <20130625100026.GB3729@localhost> (raw)
In-Reply-To: <20130625074617.4665.91288.stgit@localhost>
On Tue, Jun 25, 2013 at 09:46:17AM +0200, Giuseppe Longo wrote:
> Memory leak in function nft_rule_list_cb fixed.
Applied, thanks Giuseppe.
next prev parent reply other threads:[~2013-06-25 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 7:46 [PATCH 1/2] nft: print counter issues Giuseppe Longo
2013-06-25 7:46 ` [PATCH 2/2] nft: mem leak in nft_rule_list_cb Giuseppe Longo
2013-06-25 10:00 ` Pablo Neira Ayuso [this message]
2013-06-25 10:00 ` [PATCH 1/2] nft: print counter issues 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=20130625100026.GB3729@localhost \
--to=pablo@netfilter.org \
--cc=giuseppelng@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 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.