From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Michal Kubecek <mkubecek@suse.cz>
Cc: Florian Westphal <fw@strlen.de>,
netfilter-devel@vger.kernel.org, hawkes@google.com
Subject: Re: [PATCH nf] netfilter: x_tables: deal with bogus nextoffset values
Date: Fri, 18 Mar 2016 23:02:00 +0100 [thread overview]
Message-ID: <20160318220200.GA1574@salvia> (raw)
In-Reply-To: <20160318130340.GA9843@unicorn.suse.cz>
Hi Michal,
On Fri, Mar 18, 2016 at 02:03:40PM +0100, Michal Kubecek wrote:
> I can't see this patch neither in nf nor in nf-next even if the other
> one (netfilter: x_tables: check for size overflow) is in nf-next. Was it
> omitted on purpose or is it a mistake?
We've been considering different solutions for this, so this is still
under debate, just proposed a new one here:
http://patchwork.ozlabs.org/patch/599721/
Thanks.
prev parent reply other threads:[~2016-03-18 22:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 0:56 [PATCH nf] netfilter: x_tables: deal with bogus nextoffset values Florian Westphal
2016-03-10 14:12 ` Pablo Neira Ayuso
2016-03-10 14:41 ` Ben Hawkes
2016-03-10 16:22 ` Pablo Neira Ayuso
2016-03-18 13:03 ` Michal Kubecek
2016-03-18 22:02 ` 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=20160318220200.GA1574@salvia \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=hawkes@google.com \
--cc=mkubecek@suse.cz \
--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).