netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <simon.horman@netronome.com>
To: Jarno Rajahalme <jarno@ovn.org>
Cc: netdev@vger.kernel.org, dev@openvswitch.org,
	netfilter-devel@vger.kernel.org
Subject: Re: [ovs-dev] [PATCH net-next v3 2/8] netfilter: Factor out nf_ct_get_info().
Date: Thu, 26 Nov 2015 15:18:39 +0900	[thread overview]
Message-ID: <20151126061836.GA22390@vergenet.net> (raw)
In-Reply-To: <1448496501-109561-3-git-send-email-jarno@ovn.org>

On Wed, Nov 25, 2015 at 04:08:15PM -0800, Jarno Rajahalme wrote:
> Define a new inline function to map conntrack status to enum
> ip_conntrack_info.  This removes the need to otherwise duplicate this
> code in a later patch ("openvswitch: Find existing conntrack entry
> after upcall.").
> 
> Signed-off-by: Jarno Rajahalme <jarno@ovn.org>

Reviewed-by: Simon Horman <simon.horman@netronome.com>

> ---
>  include/net/netfilter/nf_conntrack.h | 15 +++++++++++++++
>  net/netfilter/nf_conntrack_core.c    | 22 +++-------------------
>  2 files changed, 18 insertions(+), 19 deletions(-)
> 
> diff --git a/include/net/netfilter/nf_conntrack.h b/include/net/netfilter/nf_conntrack.h
> index fde4068..b3de10e 100644
> --- a/include/net/netfilter/nf_conntrack.h
> +++ b/include/net/netfilter/nf_conntrack.h
> @@ -125,6 +125,21 @@ nf_ct_tuplehash_to_ctrack(const struct nf_conntrack_tuple_hash *hash)
>  			    tuplehash[hash->tuple.dst.dir]);
>  }
>  
> +static inline enum ip_conntrack_info
> +nf_ct_get_info(const struct nf_conntrack_tuple_hash *h)
> +{
> +	const struct nf_conn *ct = nf_ct_tuplehash_to_ctrack(h);
> +
> +	if (NF_CT_DIRECTION(h) == IP_CT_DIR_REPLY)
> +		return IP_CT_ESTABLISHED_REPLY;
> +	/* Once we've had two way comms, always ESTABLISHED. */
> +	if (test_bit(IPS_SEEN_REPLY_BIT, &ct->status))
> +		return IP_CT_ESTABLISHED;
> +	if (test_bit(IPS_EXPECTED_BIT, &ct->status))
> +		return IP_CT_RELATED;
> +	return IP_CT_NEW;
> +}
> +
>  static inline u_int16_t nf_ct_l3num(const struct nf_conn *ct)
>  {
>  	return ct->tuplehash[IP_CT_DIR_ORIGINAL].tuple.src.l3num;
> diff --git a/net/netfilter/nf_conntrack_core.c b/net/netfilter/nf_conntrack_core.c
> index 3cb3cb8..70ddbd8 100644
> --- a/net/netfilter/nf_conntrack_core.c
> +++ b/net/netfilter/nf_conntrack_core.c
> @@ -1056,25 +1056,9 @@ resolve_normal_ct(struct net *net, struct nf_conn *tmpl,
>  	ct = nf_ct_tuplehash_to_ctrack(h);
>  
>  	/* It exists; we have (non-exclusive) reference. */
> -	if (NF_CT_DIRECTION(h) == IP_CT_DIR_REPLY) {
> -		*ctinfo = IP_CT_ESTABLISHED_REPLY;
> -		/* Please set reply bit if this packet OK */
> -		*set_reply = 1;
> -	} else {
> -		/* Once we've had two way comms, always ESTABLISHED. */
> -		if (test_bit(IPS_SEEN_REPLY_BIT, &ct->status)) {
> -			pr_debug("nf_conntrack_in: normal packet for %p\n", ct);
> -			*ctinfo = IP_CT_ESTABLISHED;
> -		} else if (test_bit(IPS_EXPECTED_BIT, &ct->status)) {
> -			pr_debug("nf_conntrack_in: related packet for %p\n",
> -				 ct);
> -			*ctinfo = IP_CT_RELATED;
> -		} else {
> -			pr_debug("nf_conntrack_in: new packet for %p\n", ct);
> -			*ctinfo = IP_CT_NEW;
> -		}
> -		*set_reply = 0;
> -	}
> +	*ctinfo = nf_ct_get_info(h);
> +	*set_reply = NF_CT_DIRECTION(h) == IP_CT_DIR_REPLY;
> +
>  	skb->nfct = &ct->ct_general;
>  	skb->nfctinfo = *ctinfo;
>  	return ct;
> -- 
> 2.1.4
> 
> _______________________________________________
> dev mailing list
> dev@openvswitch.org
> http://openvswitch.org/mailman/listinfo/dev

  reply	other threads:[~2015-11-26  6:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-26  0:08 [PATCH net-next v3 0/8] openvswitch: NAT support Jarno Rajahalme
2015-11-26  0:08 ` [PATCH net-next v3 2/8] netfilter: Factor out nf_ct_get_info() Jarno Rajahalme
2015-11-26  6:18   ` Simon Horman [this message]
     [not found] ` <1448496501-109561-1-git-send-email-jarno-LZ6Gd1LRuIk@public.gmane.org>
2015-11-26  0:08   ` [PATCH net-next v3 1/8] netfilter: Remove IP_CT_NEW_REPLY definition Jarno Rajahalme
2015-11-26  5:41     ` [ovs-dev] " Simon Horman
     [not found]       ` <20151126054100.GB21626-IxS8c3vjKQDk1uMJSBkQmQ@public.gmane.org>
2015-11-30 18:16         ` Jarno Rajahalme
     [not found]           ` <391067B3-D60E-43BC-B669-2DD45924E5D8-LZ6Gd1LRuIk@public.gmane.org>
2015-12-01  2:46             ` Jarno Rajahalme
2015-11-26  0:08   ` [PATCH net-next v3 3/8] netfilter: Allow calling into nat helper without skb_dst Jarno Rajahalme
2015-12-01 20:51     ` [PATCH net-next v3 3/8] netfilter: Allow calling into nat helper without skb_dst.g Pablo Neira Ayuso
2015-12-04 23:45       ` [ovs-dev] " Pravin Shelar
2015-11-26  0:08   ` [PATCH net-next v3 4/8] openvswitch: Update the CT state key only after nf_conntrack_in() Jarno Rajahalme
2015-11-26  0:08   ` [PATCH net-next v3 5/8] openvswitch: Find existing conntrack entry after upcall Jarno Rajahalme
2015-11-26  0:08 ` [PATCH net-next v3 6/8] openvswitch: Handle NF_REPEAT in conntrack action Jarno Rajahalme
2015-11-26  0:08 ` [PATCH net-next v3 7/8] openvswitch: Delay conntrack helper call for new connections Jarno Rajahalme
2015-11-26  0:08 ` [PATCH net-next v3 8/8] openvswitch: Interface with NAT Jarno Rajahalme
2015-11-26  2:39   ` kbuild test robot
2015-11-26  4:19   ` kbuild test robot

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=20151126061836.GA22390@vergenet.net \
    --to=simon.horman@netronome.com \
    --cc=dev@openvswitch.org \
    --cc=jarno@ovn.org \
    --cc=netdev@vger.kernel.org \
    --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).