Matthieu Baerts

> It is our own script that monitors the subflow status. But by accident, out script would delete endpoints and add endpoints back. That makes sense, the only thing that...

Some notes: * This warning has been added recently, see: db75a16813aabae3b78c06b1b99f5e314c1f55d3 * It means `subflow_finish_connect()` has been called with `subflow->request_mptcp` && `!subflow->conn_finished` && `!msk->allow_infinite_fallback` * `msk->allow_infinite_fallback` is set to `true`...

I suggest closing this ticket: syzbot only saw it once in ~2 months, and my syzbot machines, using different kernel config and targetting mainly MPTCP, didn't manage to reproduce it...

Of course, a few days after having closed this bug, one of my syzkaller instances managed to reproduce it 3 times on top of `export/20250514T082830` (47d01129b03a4bc683ddb6c508e16f0a824cbebc). Still without any reproducers....

Of course. Here is the last report from one hour ago, on top of `export/20250521T055604` (d6171774bd6f74afd95e0d6f19b5814da064e0bd) (still no reproducers): ``` SELinux: unrecognized netlink message: protocol=6 nlmsg_type=0 sclass=netlink_xfrm_socket pid=5302 comm=syz.7.846 netlink:...

Hi, > I'm trying to send a video stream from a client with two 4g modem interfaces to a server with one Ethernet interface. Just to be sure, is this...

@PiotrKulesza : do you still have opened questions or can we close this ticket?

I guess all questions have been answered

> This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions....

> This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions....