From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org, kaber@trash.net
Subject: Re: [PATCH V2 nf-next] netfilter: meta: add support for setting skb->pkttype
Date: Fri, 18 Dec 2015 13:07:36 +0100 [thread overview]
Message-ID: <20151218120736.GA2606@salvia> (raw)
In-Reply-To: <20151214172642.GA1365@salvia>
On Mon, Dec 14, 2015 at 06:26:42PM +0100, Pablo Neira Ayuso wrote:
> We may keep going with the existing approach, ie. just raw data with
> no semantics, then if we decide to go this path, to retain backward
> compatibility, we would need to pass two data attributes through
> netlink: one with the raw data and another with the specific datatype
> so older kernels keep handling what userspace generates.
I working on a RFC patchset that should cover these concerns above,
but I think that new infrastructure is too much for this specific
case.
So I'm reconsidering this, I'm going to apply this patch.
Thanks.
prev parent reply other threads:[~2015-12-18 12:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 17:04 [PATCH V2 nf-next] netfilter: meta: add support for setting skb->pkttype Florian Westphal
2015-12-14 11:45 ` Pablo Neira Ayuso
2015-12-14 13:38 ` Florian Westphal
2015-12-14 17:26 ` Pablo Neira Ayuso
2015-12-18 12:07 ` 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=20151218120736.GA2606@salvia \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=kaber@trash.net \
--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).