netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 nf-next 2/3] netfilter: factor out packet duplication for IPv4/IPv6
Date: Tue, 4 Aug 2015 19:27:07 +0200	[thread overview]
Message-ID: <20150804172707.GA4079@salvia> (raw)
In-Reply-To: <20150804114810.GE20471@breakpoint.cc>

On Tue, Aug 04, 2015 at 01:48:10PM +0200, Florian Westphal wrote:
> Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > Extracted from the xtables TEE target. This creates two new modules for IPv4
> > and IPv6 that are shared between the TEE target and the new nf_tables dup
> > expressions.
> 
> > diff --git a/net/ipv4/netfilter/nf_dup_ipv4.c b/net/ipv4/netfilter/nf_dup_ipv4.c
> > new file mode 100644
> > index 0000000..feba24a
> > --- /dev/null
> > +++ b/net/ipv4/netfilter/nf_dup_ipv4.c
> > +unsigned int nf_dup_ipv4(struct sk_buff *skb, unsigned int hooknum,
> > +			 const struct in_addr *gw, int oif)
> > +{
> > +	struct iphdr *iph;
> > +
> > +	if (__this_cpu_read(nf_skb_duplicated))
> > +		return XT_CONTINUE;
> 
> Nit: seems function doesn't need to return anything.
> So the use of XT_* outisde xt core can be avoided.

Unless someone else finds any other problem, I'll fix this nit here
and apply. Thanks for spotting this Florian.

  reply	other threads:[~2015-08-04 17:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04 10:27 [PATCH nf-next 1/3] netfilter: xt_TEE: get rid of WITH_CONNTRACK definition Pablo Neira Ayuso
2015-08-04 10:27 ` =?y?q?=5BPATCH=20nf-next=202/3=5D=20netfilter=3A=20factor=20out=20packet=20duplication=20for=20IPv4/IPv6?= Pablo Neira Ayuso
2015-08-04 11:48   ` [PATCH nf-next 2/3] netfilter: factor out packet duplication for IPv4/IPv6 Florian Westphal
2015-08-04 17:27     ` Pablo Neira Ayuso [this message]
2015-08-04 10:27 ` [PATCH nf-next 3/3] netfilter: nf_tables: add nft_dup expression 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=20150804172707.GA4079@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).