public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Stringer <joestringer@nicira.com>
To: netdev@vger.kernel.org, pshelar@nicira.com
Cc: tgraf@suug.ch, jrajahalme@nicira.com
Subject: [PATCHv3 net 3/4] openvswitch: Mark connections new when not confirmed.
Date: Mon, 19 Oct 2015 19:18:59 -0700	[thread overview]
Message-ID: <1445307540-6786-3-git-send-email-joestringer@nicira.com> (raw)
In-Reply-To: <1445307540-6786-1-git-send-email-joestringer@nicira.com>

New, related connections are marked as such as part of ovs_ct_lookup(),
but they are not marked as "new" if the commit flag is used. Make this
consistent by setting the "new" flag whenever !nf_ct_is_confirmed(ct).

Reported-by: Jarno Rajahalme <jrajahalme@nicira.com>
Signed-off-by: Joe Stringer <joestringer@nicira.com>
---
v2: Acked.
v3: Took a different approach to fixing the issue.
---
 net/openvswitch/conntrack.c | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/net/openvswitch/conntrack.c b/net/openvswitch/conntrack.c
index 80bf702715bb..8ad121871834 100644
--- a/net/openvswitch/conntrack.c
+++ b/net/openvswitch/conntrack.c
@@ -151,6 +151,8 @@ static void ovs_ct_update_key(const struct sk_buff *skb,
 	ct = nf_ct_get(skb, &ctinfo);
 	if (ct) {
 		state = ovs_ct_get_state(ctinfo);
+		if (!nf_ct_is_confirmed(ct))
+			state |= OVS_CS_F_NEW;
 		if (ct->master)
 			state |= OVS_CS_F_RELATED;
 		zone = nf_ct_zone(ct);
@@ -377,7 +379,7 @@ static bool skb_nfct_cached(const struct net *net, const struct sk_buff *skb,
 	return true;
 }
 
-static int __ovs_ct_lookup(struct net *net, const struct sw_flow_key *key,
+static int __ovs_ct_lookup(struct net *net, struct sw_flow_key *key,
 			   const struct ovs_conntrack_info *info,
 			   struct sk_buff *skb)
 {
@@ -408,6 +410,8 @@ static int __ovs_ct_lookup(struct net *net, const struct sw_flow_key *key,
 		}
 	}
 
+	ovs_ct_update_key(skb, key, true);
+
 	return 0;
 }
 
@@ -430,8 +434,6 @@ static int ovs_ct_lookup(struct net *net, struct sw_flow_key *key,
 		err = __ovs_ct_lookup(net, key, info, skb);
 		if (err)
 			return err;
-
-		ovs_ct_update_key(skb, key, true);
 	}
 
 	return 0;
@@ -460,8 +462,6 @@ static int ovs_ct_commit(struct net *net, struct sw_flow_key *key,
 	if (nf_conntrack_confirm(skb) != NF_ACCEPT)
 		return -EINVAL;
 
-	ovs_ct_update_key(skb, key, true);
-
 	return 0;
 }
 
-- 
2.1.4

  parent reply	other threads:[~2015-10-20  2:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20  2:18 [PATCHv3 net 1/4] openvswitch: Reject ct_state masks for unknown bits Joe Stringer
2015-10-20  2:18 ` [PATCHv3 net 2/4] openvswitch: Clarify conntrack COMMIT behaviour Joe Stringer
2015-10-20  8:37   ` Thomas Graf
2015-10-20 21:53   ` Pravin Shelar
2015-10-22  2:34   ` David Miller
2015-10-20  2:18 ` Joe Stringer [this message]
2015-10-20  8:41   ` [PATCHv3 net 3/4] openvswitch: Mark connections new when not confirmed Thomas Graf
2015-10-20 22:07   ` Pravin Shelar
2015-10-22  2:34   ` David Miller
2015-10-20  2:19 ` [PATCHv3 net 4/4] openvswitch: Serialize nested ct actions if provided Joe Stringer
2015-10-22  2:34   ` David Miller
2015-10-22  2:34 ` [PATCHv3 net 1/4] openvswitch: Reject ct_state masks for unknown bits David Miller

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=1445307540-6786-3-git-send-email-joestringer@nicira.com \
    --to=joestringer@nicira.com \
    --cc=jrajahalme@nicira.com \
    --cc=netdev@vger.kernel.org \
    --cc=pshelar@nicira.com \
    --cc=tgraf@suug.ch \
    /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