From: Aaron Conole <aconole@redhat.com>
To: Xin Long <lucien.xin@gmail.com>
Cc: network dev <netdev@vger.kernel.org>,
dev@openvswitch.org, Florian Westphal <fw@strlen.de>,
Ilya Maximets <i.maximets@ovn.org>,
Eric Dumazet <edumazet@google.com>,
kuba@kernel.org, Paolo Abeni <pabeni@redhat.com>,
davem@davemloft.net, Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [ovs-dev] [PATCH net] openvswitch: add nf_ct_is_confirmed check before assigning the helper
Date: Tue, 11 Oct 2022 09:36:33 -0400 [thread overview]
Message-ID: <f7tczayh47y.fsf@redhat.com> (raw)
In-Reply-To: <c5c9092a22a2194650222bffaf786902613deb16.1665085502.git.lucien.xin@gmail.com> (Xin Long's message of "Thu, 6 Oct 2022 15:45:02 -0400")
Xin Long <lucien.xin@gmail.com> writes:
> A WARN_ON call trace would be triggered when 'ct(commit, alg=helper)'
> applies on a confirmed connection:
>
> WARNING: CPU: 0 PID: 1251 at net/netfilter/nf_conntrack_extend.c:98
> RIP: 0010:nf_ct_ext_add+0x12d/0x150 [nf_conntrack]
> Call Trace:
> <TASK>
> nf_ct_helper_ext_add+0x12/0x60 [nf_conntrack]
> __nf_ct_try_assign_helper+0xc4/0x160 [nf_conntrack]
> __ovs_ct_lookup+0x72e/0x780 [openvswitch]
> ovs_ct_execute+0x1d8/0x920 [openvswitch]
> do_execute_actions+0x4e6/0xb60 [openvswitch]
> ovs_execute_actions+0x60/0x140 [openvswitch]
> ovs_packet_cmd_execute+0x2ad/0x310 [openvswitch]
> genl_family_rcv_msg_doit.isra.15+0x113/0x150
> genl_rcv_msg+0xef/0x1f0
>
> which can be reproduced with these OVS flows:
>
> table=0, in_port=veth1,tcp,tcp_dst=2121,ct_state=-trk
> actions=ct(commit, table=1)
> table=1, in_port=veth1,tcp,tcp_dst=2121,ct_state=+trk+new
> actions=ct(commit, alg=ftp),normal
>
> The issue was introduced by commit 248d45f1e193 ("openvswitch: Allow
> attaching helper in later commit") where it somehow removed the check
> of nf_ct_is_confirmed before asigning the helper. This patch is to fix
> it by bringing it back.
>
> Fixes: 248d45f1e193 ("openvswitch: Allow attaching helper in later commit")
> Reported-by: Pablo Neira Ayuso <pablo@netfilter.org>
> Signed-off-by: Xin Long <lucien.xin@gmail.com>
> ---
Hi Xin,
Looking at the original commit, I think this will read like a revert. I
am doing some testing now, but I think we need input from Yi-Hung to
find out what the use case is that the original fixed.
-Aaron
next prev parent reply other threads:[~2022-10-11 13:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 19:45 [PATCH net] openvswitch: add nf_ct_is_confirmed check before assigning the helper Xin Long
2022-10-11 13:33 ` Paolo Abeni
2022-10-11 13:36 ` Aaron Conole [this message]
2022-10-11 14:06 ` [ovs-dev] " Aaron Conole
2022-10-11 14:22 ` Xin Long
2022-10-12 12:15 ` Aaron Conole
2022-10-13 1:50 ` patchwork-bot+netdevbpf
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=f7tczayh47y.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=i.maximets@ovn.org \
--cc=kuba@kernel.org \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.