From: Paolo Abeni <pabeni at redhat.com>
To: mptcp at lists.01.org
Subject: [MPTCP] [PATCH net-next 0/2] The current export branch suffers of the following issue:
Date: Wed, 14 Oct 2020 19:15:14 +0200 [thread overview]
Message-ID: <cover.1602693911.git.pabeni@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]
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(-)
--
2.26.2
reply other threads:[~2020-10-14 17:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1602693911.git.pabeni@redhat.com \
--to=unknown@example.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.