From: Ilya Maximets <i.maximets@ovn.org>
To: Eric Dumazet <edumazet@google.com>
Cc: i.maximets@ovn.org,
Steffen Klassert <steffen.klassert@secunet.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Florian Westphal <fw@strlen.de>, netdev <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
dev@openvswitch.org, LKML <linux-kernel@vger.kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net] net: ensure all external references are released in deferred skbuffs
Date: Wed, 22 Jun 2022 20:19:08 +0200 [thread overview]
Message-ID: <673a6f2b-dab2-e00f-b37c-15f8775b2121@ovn.org> (raw)
In-Reply-To: <CANn89i+5pWbXyFBnMqdfz6SqRV9enFNHbcd_2irJub1Ag7vxNw@mail.gmail.com>
On 6/22/22 19:03, Eric Dumazet wrote:
> On Wed, Jun 22, 2022 at 6:47 PM Eric Dumazet <edumazet@google.com> wrote:
>>
>> On Wed, Jun 22, 2022 at 6:39 PM Eric Dumazet <edumazet@google.com> wrote:
>>>
>>> On Wed, Jun 22, 2022 at 6:29 PM Eric Dumazet <edumazet@google.com> wrote:
>>>>
>>>> On Wed, Jun 22, 2022 at 4:26 PM Ilya Maximets <i.maximets@ovn.org> wrote:
>>>>>
>>>>> On 6/22/22 13:43, Eric Dumazet wrote:
>>>>
>>>>>
>>>>> I tested the patch below and it seems to fix the issue seen
>>>>> with OVS testsuite. Though it's not obvious for me why this
>>>>> happens. Can you explain a bit more?
>>>>
>>>> Anyway, I am not sure we can call nf_reset_ct(skb) that early.
>>>>
>>>> git log seems to say that xfrm check needs to be done before
>>>> nf_reset_ct(skb), I have no idea why.
>>>
>>> Additional remark: In IPv6 side, xfrm6_policy_check() _is_ called
>>> after nf_reset_ct(skb)
>>>
>>> Steffen, do you have some comments ?
>>>
>>> Some context:
>>> commit b59c270104f03960069596722fea70340579244d
>>> Author: Patrick McHardy <kaber@trash.net>
>>> Date: Fri Jan 6 23:06:10 2006 -0800
>>>
>>> [NETFILTER]: Keep conntrack reference until IPsec policy checks are done
>>>
>>> Keep the conntrack reference until policy checks have been performed for
>>> IPsec NAT support. The reference needs to be dropped before a packet is
>>> queued to avoid having the conntrack module unloadable.
>>>
>>> Signed-off-by: Patrick McHardy <kaber@trash.net>
>>> Signed-off-by: David S. Miller <davem@davemloft.net>
>>>
>>
>> Oh well... __xfrm_policy_check() has :
>>
>> nf_nat_decode_session(skb, &fl, family);
>>
>> This answers my questions.
>>
>> This means we are probably missing at least one XFRM check in TCP
>> stack in some cases.
>> (Only after adding this XFRM check we can call nf_reset_ct(skb))
>>
>
> Maybe this will help ?
I tested this patch and it seems to fix the OVS problem.
I did not test the xfrm part of it.
Will you post an official patch?
>
> diff --git a/net/ipv4/tcp_ipv4.c b/net/ipv4/tcp_ipv4.c
> index fe8f23b95d32ca4a35d05166d471327bc608fa91..49c1348e40b6c7b6a98b54d716f29c948e00ba33
> 100644
> --- a/net/ipv4/tcp_ipv4.c
> +++ b/net/ipv4/tcp_ipv4.c
> @@ -2019,12 +2019,19 @@ int tcp_v4_rcv(struct sk_buff *skb)
> if (nsk == sk) {
> reqsk_put(req);
> tcp_v4_restore_cb(skb);
> - } else if (tcp_child_process(sk, nsk, skb)) {
> - tcp_v4_send_reset(nsk, skb);
> - goto discard_and_relse;
> } else {
> - sock_put(sk);
> - return 0;
> + if (!xfrm4_policy_check(nsk, XFRM_POLICY_IN, skb)) {
> + drop_reason = SKB_DROP_REASON_XFRM_POLICY;
> + goto discard_and_relse;
> + }
> + nf_reset_ct(skb);
> + if (tcp_child_process(sk, nsk, skb)) {
> + tcp_v4_send_reset(nsk, skb);
> + goto discard_and_relse;
> + } else {
> + sock_put(sk);
> + return 0;
> + }
> }
> }
next prev parent reply other threads:[~2022-06-22 18:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 0:39 Ilya Maximets
2022-06-22 10:02 ` Eric Dumazet
2022-06-22 10:15 ` Eric Dumazet
2022-06-22 10:28 ` Florian Westphal
2022-06-22 10:36 ` Eric Dumazet
2022-06-22 11:32 ` Ilya Maximets
2022-06-22 11:43 ` Eric Dumazet
2022-06-22 14:26 ` Ilya Maximets
2022-06-22 14:35 ` Eric Dumazet
2022-06-22 18:09 ` Ilya Maximets
2022-06-22 16:29 ` Eric Dumazet
2022-06-22 16:39 ` Eric Dumazet
2022-06-22 16:47 ` Eric Dumazet
2022-06-22 17:03 ` Eric Dumazet
2022-06-22 18:19 ` Ilya Maximets [this message]
2022-06-22 19:04 ` Eric Dumazet
2022-06-22 19:27 ` Eric Dumazet
2022-06-22 21:12 ` Ilya Maximets
2023-09-22 13:26 ` Ilya Maximets
2023-09-22 19:07 ` Ilya Maximets
2023-09-22 21:09 ` Ilya Maximets
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=673a6f2b-dab2-e00f-b37c-15f8775b2121@ovn.org \
--to=i.maximets@ovn.org \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.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
all inboxes | Powered by JetHome®