From: Matthieu Baerts <matttbe@kernel.org>
To: netdev-bot+sinfo@kernel.org
Cc: Mat Martineau <martineau@kernel.org>,
Geliang Tang <geliang@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Christoph Paasch <cpaasch@openai.com>,
Chris Mason <mason@kernel.org>,
netdev@vger.kernel.org, mptcp@lists.linux.dev,
linux-kernel@vger.kernel.org,
Yilin Zhang <yilinzhang@moonshot.ai>,
stable@vger.kernel.org,
Kimi Security Team <bug-report@moonshot.ai>,
Jiayuan Chen <jiayuan.chen@linux.dev>
Subject: Re: [PATCH net v4] mptcp: do not use Fast Open on MP_JOIN subflows
Date: Fri, 30 Oct 2026 23:12:57 +0100 [thread overview]
Message-ID: <931d99cc-cc2e-4967-89e7-298d9a3fd0e1@kernel.org> (raw)
In-Reply-To: <179339809972.3286.6931292097714769277@kernel.org>
On 30/10/2026 23:08, netdev-bot+sinfo@kernel.org wrote:
> Hi!
>
> This is an automated message. This series looks like a fix, but its
> commit messages seem to be missing some information:
>
> - Whether the issue was actually triggered, or is only theoretical
> (e.g. found by code inspection). If it was triggered please include
> the symptoms, like the stack trace or error messages.
Indeed, I forgot to add: the same reproducer from v1 still applies: the
issue was actually triggered. The symptoms are described in the commit
message.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2026-10-30 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 22:03 Matthieu Baerts (NGI0)
2026-10-30 22:08 ` netdev-bot+sinfo
2026-10-30 22:12 ` Matthieu Baerts [this message]
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=931d99cc-cc2e-4967-89e7-298d9a3fd0e1@kernel.org \
--to=matttbe@kernel.org \
--cc=bug-report@moonshot.ai \
--cc=cpaasch@openai.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=jiayuan.chen@linux.dev \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=mason@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev-bot+sinfo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=yilinzhang@moonshot.ai \
/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®