From: Pravin Shelar <pshelar@ovn.org>
To: Flavio Leitner <fbl@sysclose.org>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
Joe Stringer <joe@ovn.org>, ovs dev <dev@openvswitch.org>,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH net-next] openvswitch: add seqadj extension when NAT is used.
Date: Sat, 23 Mar 2019 12:32:37 -0700 [thread overview]
Message-ID: <CAOrHB_CActmZPWipq6chM0SXAkTsODuHFyVMTdL8idCjB-Vecw@mail.gmail.com> (raw)
In-Reply-To: <20190321165224.24118-1-fbl@sysclose.org>
On Thu, Mar 21, 2019 at 9:52 AM Flavio Leitner <fbl@sysclose.org> wrote:
>
> When the conntrack is initialized, there is no helper attached
> yet so the nat info initialization (nf_nat_setup_info) skips
> adding the seqadj ext.
>
> A helper is attached later when the conntrack is not confirmed
> but is going to be committed. In this case, if NAT is needed then
> adds the seqadj ext as well.
>
> Fixes: 16ec3d4fbb96 ("openvswitch: Fix cached ct with helper.")
> Signed-off-by: Flavio Leitner <fbl@sysclose.org>
> ---
> net/openvswitch/conntrack.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
I am not able to apply this patch.
> diff --git a/net/openvswitch/conntrack.c b/net/openvswitch/conntrack.c
> index 1b6896896fff..a7664515c943 100644
> --- a/net/openvswitch/conntrack.c
> +++ b/net/openvswitch/conntrack.c
> @@ -990,6 +990,11 @@ static int __ovs_ct_lookup(struct net *net, struct sw_flow_key *key,
> GFP_ATOMIC);
> if (err)
> return err;
> +
> + if (info->nat && nfct_help(ct) && !nfct_seqadj(ct)) {
Given helper is just assigned, is nfct_help() check required here?
> + if (!nfct_seqadj_ext_add(ct))
> + return -EINVAL;
> + }
> }
>
> /* Call the helper only if:
> --
> 2.20.1
>
>
>
next prev parent reply other threads:[~2019-03-23 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 16:52 [PATCH net-next] openvswitch: add seqadj extension when NAT is used Flavio Leitner
2019-03-23 19:32 ` Pravin Shelar [this message]
2019-03-25 14:38 ` Flavio Leitner
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=CAOrHB_CActmZPWipq6chM0SXAkTsODuHFyVMTdL8idCjB-Vecw@mail.gmail.com \
--to=pshelar@ovn.org \
--cc=dev@openvswitch.org \
--cc=fbl@sysclose.org \
--cc=joe@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).