public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Graf <tgraf@suug.ch>
To: Joe Stringer <joestringer@nicira.com>
Cc: netdev@vger.kernel.org, pshelar@nicira.com, jrajahalme@nicira.com
Subject: Re: [PATCHv3 net 3/4] openvswitch: Mark connections new when not confirmed.
Date: Tue, 20 Oct 2015 10:41:26 +0200	[thread overview]
Message-ID: <20151020084126.GB25435@pox.localdomain> (raw)
In-Reply-To: <1445307540-6786-3-git-send-email-joestringer@nicira.com>

On 10/19/15 at 07:18pm, Joe Stringer wrote:
> 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.

Acked-by: Thomas Graf <tgraf@suug.ch>

  reply	other threads:[~2015-10-20  8:41 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 ` [PATCHv3 net 3/4] openvswitch: Mark connections new when not confirmed Joe Stringer
2015-10-20  8:41   ` Thomas Graf [this message]
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=20151020084126.GB25435@pox.localdomain \
    --to=tgraf@suug.ch \
    --cc=joestringer@nicira.com \
    --cc=jrajahalme@nicira.com \
    --cc=netdev@vger.kernel.org \
    --cc=pshelar@nicira.com \
    /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