From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Munehisa Kamata <kamatam@amazon.com>
Cc: netfilter-devel@vger.kernel.org, msw@amazon.com,
aliguori@amazon.com, kaber@trash.net, kadlec@blackhole.kfki.hu,
davem@davemloft.net,
Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
Subject: Re: [PATCH] netfilter: add missing NULL pointer check
Date: Wed, 28 Oct 2015 03:44:39 +0100 [thread overview]
Message-ID: <20151028024439.GA3222@salvia> (raw)
In-Reply-To: <1445911852-4838-1-git-send-email-kamatam@amazon.com>
On Mon, Oct 26, 2015 at 07:10:52PM -0700, Munehisa Kamata wrote:
> Commit 8b13eddfdf04cbfa561725cfc42d6868fe896f56 ("netfilter: refactor NAT
> redirect IPv4 to use it from nf_tables") has introduced a trivial logic
> change which can result in the following crash.
This seems to have accidentally slipped through while adding redirect
support for nf_tables.
Applied, thanks.
prev parent reply other threads:[~2015-10-28 2:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 2:10 [PATCH] netfilter: add missing NULL pointer check Munehisa Kamata
2015-10-28 2:44 ` 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=20151028024439.GA3222@salvia \
--to=pablo@netfilter.org \
--cc=aliguori@amazon.com \
--cc=arturo.borrero.glez@gmail.com \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=kamatam@amazon.com \
--cc=msw@amazon.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).