The current export branch suffers of the following issue:
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | tcp: factor out tcp_build_frag()include/ net/ | +70 | 1 reply | |
| 2/2 | mptcp: use tcp_build_frag()net/ | +8 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [MPTCP] [PATCH net-next 0/2] The current export branch suffers of the following issue:
https://github.com/multipath-tcp/mptcp_net-next/issues/97
To fix the above, MPTCP needs to be able to cope with memory allocation failure in do_tcp_sendpages().
In this iteration the patches are rebased on top of:
"bpf:selftests: add bpf_mptcp_sock() verifier tests"
and should apply without fuzz on net-next.
patch 1/2 went through some lifting to be hopefully more acceptable upstream.
This will cause a few conflicts in later patch, specifically in "mptcp: move page frag allocation in mptcp_sendmsg()". Possibly the simpler/better would be squashing 2/2 in there.
The plan is to send 1/2 and "tcp: factor out __tcp_close() helper" as RFC upstream soon/while net-next is closed to try to understand if that could be acceptable. The 2 TCP patches alone, without the full series to hopefully make the review simpler/less cumbersome.
Any feedback more than welcome!!!
Paolo Abeni (2):
tcp: factor out tcp_build_frag()
mptcp: use tcp_build_frag()
include/net/tcp.h | 3 ++ net/ipv4/tcp.c | 119 ++++++++++++++++++++++++------------------- net/mptcp/protocol.c | 25 +++------ 3 files changed, 78 insertions(+), 69 deletions(-)
Signature · 1 line
2.26.2