From: Davide Caratti <dcara...@redhat.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.
