* MPTCP deadlocks
@ 2025-12-03 15:35 Jakub Kicinski
2025-12-03 17:37 ` Matthieu Baerts
0 siblings, 1 reply; 3+ messages in thread
From: Jakub Kicinski @ 2025-12-03 15:35 UTC (permalink / raw)
To: Paolo Abeni, Matthieu Baerts; +Cc: netdev@vger.kernel.org
Hi!
Not sure if its the new machines or some of the recent work in MPTCP
but we hit a deadlock in the tests a couple of times:
stderr of join.sh:
https://netdev-ctrl.bots.linux.dev/logs/vmksft/mptcp-dbg/results/412720/1-mptcp-join-sh/stderr
decoded:
https://netdev-ctrl.bots.linux.dev/logs/vmksft/mptcp-dbg/results/412720/vm-crash-thr0-0
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: MPTCP deadlocks
2025-12-03 15:35 MPTCP deadlocks Jakub Kicinski
@ 2025-12-03 17:37 ` Matthieu Baerts
2025-12-03 18:30 ` Paolo Abeni
0 siblings, 1 reply; 3+ messages in thread
From: Matthieu Baerts @ 2025-12-03 17:37 UTC (permalink / raw)
To: Jakub Kicinski, Paolo Abeni; +Cc: netdev@vger.kernel.org
Hi Jakub,
On 03/12/2025 16:35, Jakub Kicinski wrote:
> Not sure if its the new machines or some of the recent work in MPTCP
> but we hit a deadlock in the tests a couple of times:
Thank you for the message, I didn't notice that, and I didn't see this
issue in our CI. So maybe due to both the new machines and the recent work.
I will check if one of my syzkaller instances didn't find the same bug,
hopefully with a reproducer.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: MPTCP deadlocks
2025-12-03 17:37 ` Matthieu Baerts
@ 2025-12-03 18:30 ` Paolo Abeni
0 siblings, 0 replies; 3+ messages in thread
From: Paolo Abeni @ 2025-12-03 18:30 UTC (permalink / raw)
To: Matthieu Baerts, Jakub Kicinski; +Cc: netdev@vger.kernel.org
On 12/3/25 6:37 PM, Matthieu Baerts wrote:
> On 03/12/2025 16:35, Jakub Kicinski wrote:
>> Not sure if its the new machines or some of the recent work in MPTCP
>> but we hit a deadlock in the tests a couple of times:
>
> Thank you for the message, I didn't notice that, and I didn't see this
> issue in our CI. So maybe due to both the new machines and the recent work.
>
> I will check if one of my syzkaller instances didn't find the same bug,
> hopefully with a reproducer.
caused by:
ommit f8a1d9b18c5efc76784f5a326e905f641f839894
Author: Paolo Abeni <pabeni@redhat.com>
Date: Mon Jul 14 18:41:44 2025 +0200
mptcp: make fallback action and fallback decision atomic
I think it's just quite unlikely to hit the relevant code path with the
suitable status to trigger the bug.
@Matttbe: if it's ok I'll send a patch directly to net
/P
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2025-12-03 18:30 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-12-03 15:35 MPTCP deadlocks Jakub Kicinski
2025-12-03 17:37 ` Matthieu Baerts
2025-12-03 18:30 ` Paolo Abeni
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 NNTP newsgroup(s).