netdev - Re: MPTCP deadlocks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <89b15d8b-f145-40f5-a56a-07b73b3ea899@redhat.com>
Date: Wed, 3 Dec 2025 19:30:30 +0100
From: Paolo Abeni <pabeni@...hat.com>
To: Matthieu Baerts <matttbe@...nel.org>, Jakub Kicinski <kuba@...nel.org>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: MPTCP deadlocks

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@...hat.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