Hi Paolo -

On Thursday we talked about patches to send next:

Patches to send to netdev:
     - net-next:
         - 2 series are ready:
             - Paolo's series (backup / scheduler):
                 → maybe best to wait, see issues/219
             - Yonglong & Geliang's series (ADD_ADDR/RM_ADDR refactor)

I saw your comment on 
https://github.com/multipath-tcp/mptcp_net-next/issues/219, you mentioned 
that the two newest patches on the export branch looked like they were not 
related to the divide error seen by syzkaller. Any reason to wait on 
sending the active-backup series earlier in the export branch:

9058115c3ff7 selftests: mptcp: add testcase for active-back
8a8c8b5711d7 mptcp: backup flag from incoming MPJ ack option
1f05f7524500 mptcp: add mibs for stale subflows processing
f1abc22dbc32 mptcp: faster active backup recovery
69a226d4b8c4 mptcp: cleanup sysctl data and helpers
f0699e78732e mptcp: handle pending data on closed subflow
167e8cf026aa mptcp: less aggressive retransmission strategy
77477273b6de mptcp: more accurate timeout

?


Thanks,

--
Mat Martineau
Intel