Skip to contentSkip to conversation

MPTCP deadlocks

DISCUSSION Jakub Kicinski 3 participants 3 messages Dec 3, 2025

Subsystems (2)
lore
Share & tools
lore
#1 lore raw

Hi Jakub,

Quoted 2 lines · Jakub Kicinski

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

Signature · 1 line
Sponsored by the NGI0 Core fund.
maintainer
#2 lore raw
Quoted 9 lines · Matthieu Baerts
Quoted 2 lines · Jakub Kicinski

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 <[email protected]>
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