From: "liujian (CE)" <liujian56@huawei.com>
To: John Fastabend <john.fastabend@gmail.com>,
Jakub Sitnicki <jakub@cloudflare.com>,
Eric Dumazet <edumazet@google.com>, davem <davem@davemloft.net>,
"yoshfuji@linux-ipv6.org" <yoshfuji@linux-ipv6.org>,
"dsahern@kernel.org" <dsahern@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: netdev <netdev@vger.kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>
Subject: [bug report] one possible out-of-order issue in sockmap
Date: Sat, 24 Sep 2022 07:59:15 +0000 [thread overview]
Message-ID: <061d068ccd6f4db899d095cd61f52114@huawei.com> (raw)
Hello,
I had a scp failure problem here. I analyze the code, and the reasons may be as follows:
From commit e7a5f1f1cd00 ("bpf/sockmap: Read psock ingress_msg before
sk_receive_queue", if we use sockops (BPF_SOCK_OPS_ACTIVE_ESTABLISHED_CB
and BPF_SOCK_OPS_PASSIVE_ESTABLISHED_CB) to enable socket's sockmap
function, and don't enable strparse and verdict function, the out-of-order
problem may occur in the following process.
client SK server SK
--------------------------------------------------------------------------
tcp_rcv_synsent_state_process
tcp_finish_connect
tcp_init_transfer
tcp_set_state(sk, TCP_ESTABLISHED);
// insert SK to sockmap
wake up waitter
tcp_send_ack
tcp_bpf_sendmsg(msgA)
// msgA will go tcp stack
tcp_rcv_state_process
tcp_init_transfer
//insert SK to sockmap
tcp_set_state(sk,
TCP_ESTABLISHED)
wake up waitter
tcp_bpf_sendmsg(msgB)
// msgB go sockmap
tcp_bpf_recvmsg
//msgB, out-of-order
tcp_bpf_recvmsg
//msgA, out-of-order
Even if msgA arrives earlier than msgB (in most cases), tcp_bpf_recvmsg receives msg from the psock queue first.
The worst case is that msgA waits for serverSK to change to TCP_ESTABLISHED in the protocol stack. msgA may arrive at the serverSK receive queue later than msgB.
If msgA befor than msgB,
If the ACK packets of the three-way TCP handshake are dropped for a period of time, the OOO problem is easily reproduced.
iptables -A INPUT -p tcp -m tcp --dport 5006 --tcp-flags SYN,RST,ACK,FIN ACK -j DROP
...
iptables -D INPUT -p tcp -m tcp --dport 5006 --tcp-flags SYN,RST,ACK,FIN ACK -j DROP
Best Wishes
Liu Jian
next reply other threads:[~2022-09-24 7:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-24 7:59 liujian (CE) [this message]
2022-09-25 18:25 ` [bug report] one possible out-of-order issue in sockmap Cong Wang
2022-09-26 1:34 ` liujian (CE)
2022-09-26 21:16 ` John Fastabend
2022-09-27 2:15 ` liujian (CE)
2022-09-28 18:31 ` John Fastabend
2022-11-26 7:12 ` liujian (CE)
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=061d068ccd6f4db899d095cd61f52114@huawei.com \
--to=liujian56@huawei.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yoshfuji@linux-ipv6.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.