From: Kyuwon Cho <kyuwoncho18@gmail.com>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: Mat Martineau <martineau@kernel.org>,
Geliang Tang <geliang@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Simon Horman <horms@kernel.org>,
mptcp@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] mptcp: pm: WARNING in mptcp_check_listen_stop() when listen fails on a new endpoint listener
Date: Wed, 18 Nov 2026 10:31:17 -0800 (PST) [thread overview]
Message-ID: <179502653236.3033236.9177220287548482679@gmail.com> (raw)
In-Reply-To: <5d651146-b21d-44da-9f15-860f0c9c2dc5@kernel.org>
Hi Matt,
On 18/11/2026 19:18, Matthieu Baerts wrote:
> Please always decode stacktraces with ./scripts/decode_stacktrace.sh.
I'll keep that in mind and decode them in my next reports.
> Out of curiosity: if your LLM has already analysed the root cause and
> has a reproducer, why not ask to generate a fix and send this patch
> instead of the bug report?
I'm more used to communities like LLVM, which are cautious about
LLM-generated patches, and I was hesitant to send a fix for code I
don't know well, made in a way I couldn't fully judge. So I only sent
the root cause analysis. Thanks for explaining; I'll send a tested
patch with later reports when I can.
For this one we do have a small candidate fix, tested with the
reproducer: it puts the MPTCP socket back to TCP_CLOSE when
__inet_listen_sk() fails. Since you already have a fix for v2, would it
still help if we posted it, or should we leave it to your series?
Thanks,
Kyuwon Cho
prev parent reply other threads:[~2026-11-18 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 16:59 [BUG] mptcp: pm: WARNING in mptcp_check_listen_stop() when listen fails on a new endpoint listener Kyuwon Cho
2026-11-18 18:18 ` Matthieu Baerts
2026-11-18 18:31 ` Kyuwon Cho [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=179502653236.3033236.9177220287548482679@gmail.com \
--to=kyuwoncho18@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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