netdev - Re: [PATCH net-next 0/6] MPTCP: improve fallback to TCP

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: <20200629.172954.2096977916313984108.davem@davemloft.net>
Date:   Mon, 29 Jun 2020 17:29:54 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     dcaratti@...hat.com
Cc:     mathew.j.martineau@...ux.intel.com, matthieu.baerts@...sares.net,
        kuba@...nel.org, netdev@...r.kernel.org, mptcp@...ts.01.org
Subject: Re: [PATCH net-next 0/6] MPTCP: improve fallback to TCP

From: Davide Caratti <dcaratti@...hat.com>
Date: Mon, 29 Jun 2020 22:26:19 +0200

> there are situations where MPTCP sockets should fall-back to regular TCP:
> this series reworks the fallback code to pursue the following goals:
> 
> 1) cleanup the non fallback code, removing most of 'if (<fallback>)' in
>    the data path
> 2) improve performance for non-fallback sockets, avoiding locks in poll()
> 
> further work will also leverage on this changes to achieve:
> 
> a) more consistent behavior of gestockopt()/setsockopt() on passive sockets
>    after fallback
> b) support for "infinite maps" as per RFC8684, section 3.7
> 
> the series is made of the following items:
> 
> - patch 1 lets sendmsg() / recvmsg() / poll() use the main socket also
>   after fallback
> - patch 2 fixes 'simultaneous connect' scenario after fallback. The
>   problem was present also before the rework, but the fix is much easier
>   to implement after patch 1
> - patch 3, 4, 5 are clean-ups for code that is no more needed after the
>   fallback rework
> - patch 6 fixes a race condition between close() and poll(). The problem
>   was theoretically present before the rework, but it became almost
>   systematic after patch 1

Series applied to net-next, thank you.