From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Liping Zhang <zlpnobody@163.com>
Cc: netfilter-devel@vger.kernel.org,
Liping Zhang <liping.zhang@spreadtrum.com>
Subject: Re: [PATCH nf] netfilter: nf_tables: fix memory leak if expr init fails
Date: Thu, 23 Jun 2016 13:03:04 +0200 [thread overview]
Message-ID: <20160623110304.GA2312@salvia> (raw)
In-Reply-To: <1466428305-58285-1-git-send-email-zlpnobody@163.com>
On Mon, Jun 20, 2016 at 09:11:45PM +0800, Liping Zhang wrote:
> From: Liping Zhang <liping.zhang@spreadtrum.com>
>
> If expr init fails then we need to free it.
>
> So when the user add a nft rule as follows:
> # nft add rule filter input tcp dport 22 flow table ssh \
> { ip saddr limit rate 0/second }
> memory leak will happen.
Applied to nf, thanks!
prev parent reply other threads:[~2016-06-23 11:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 13:11 [PATCH nf] netfilter: nf_tables: fix memory leak if expr init fails Liping Zhang
2016-06-23 11:03 ` 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=20160623110304.GA2312@salvia \
--to=pablo@netfilter.org \
--cc=liping.zhang@spreadtrum.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=zlpnobody@163.com \
/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).