From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Network Development <netdev@vger.kernel.org>,
bpf <bpf@vger.kernel.org>,
MPTCP Upstream <mptcp@lists.linux.dev>,
Matthieu Baerts <matttbe@kernel.org>,
Mat Martineau <martineau@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Martin KaFai Lau <martin.lau@kernel.org>
Subject: mptcp splat
Date: Wed, 27 Mar 2024 09:43:09 -0700 [thread overview]
Message-ID: <CAADnVQKCxxETthqDpcE1xMGwa5au8JuLr_49QuwemL7uBKfiVg@mail.gmail.com> (raw)
Hi,
I ffwded bpf tree with the recent net fixes and caught this:
[ 48.386337] WARNING: CPU: 32 PID: 3276 at net/mptcp/subflow.c:1430
subflow_data_ready+0x147/0x1c0
[ 48.392012] Modules linked in: dummy bpf_testmod(O) [last unloaded:
bpf_test_no_cfi(O)]
[ 48.396609] CPU: 32 PID: 3276 Comm: test_progs Tainted: G
O 6.8.0-12873-g2c43c33bfd23 #1014
#[ 48.467143] Call Trace:
[ 48.469094] <TASK>
[ 48.472159] ? __warn+0x80/0x180
[ 48.475019] ? subflow_data_ready+0x147/0x1c0
[ 48.478068] ? report_bug+0x189/0x1c0
[ 48.480725] ? handle_bug+0x36/0x70
[ 48.483061] ? exc_invalid_op+0x13/0x60
[ 48.485809] ? asm_exc_invalid_op+0x16/0x20
[ 48.488754] ? subflow_data_ready+0x147/0x1c0
[ 48.492159] mptcp_set_rcvlowat+0x79/0x1d0
[ 48.495026] sk_setsockopt+0x6c0/0x1540
It doesn't reproduce all the time though.
Some race?
Known issue?
next reply other threads:[~2024-03-27 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 16:43 Alexei Starovoitov [this message]
2024-03-27 16:56 ` mptcp splat Paolo Abeni
2024-03-27 17:00 ` Alexei Starovoitov
2024-03-27 18:32 ` Paolo Abeni
2024-03-27 18:45 ` Mat Martineau
2024-03-27 18:50 ` Alexei Starovoitov
2024-03-27 22:16 ` Martin KaFai Lau
2024-03-28 17:35 ` Matthieu Baerts
2024-03-29 16:26 ` Alexei Starovoitov
2024-03-29 16:34 ` Paolo Abeni
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=CAADnVQKCxxETthqDpcE1xMGwa5au8JuLr_49QuwemL7uBKfiVg@mail.gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=martin.lau@kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@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 read-only IMAP folder(s) and NNTP newsgroup(s).