MPTCP Linux Development
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: mptcp@lists.linux.dev
Subject: [PATCH mptcp-next 0/9] mptcp: refactor first subflow init
Date: Fri, 13 Jan 2023 19:20:47 +0100	[thread overview]
Message-ID: <cover.1673629755.git.pabeni@redhat.com> (raw)

This is the needed refactor for the selinux fixes, as discussed on
the ML.

The main change, introduced by patch 6/9 consist in moving the first
subflow initialization from the msk init callback into the mptcp
syscall needing such data (namely: bind, listen, connect). 

Patch 4 and 5 allow making such change smaller.

Patches 7, 8, 9 are not strictly needed, but are some nice to have
follow-up, cleaning-up the related code.

Specifically patch 8 closes issues/290, but requires some additional
pre-req (patches 1-3), which in turn are also nice to have IMHO.

Sharing after little testing to get feedback and let the bot massage
the new code: patch 1 and 7 can have subtle effect, I would like to
have syzkaller digest them for a while.

I'll rebase the selinux patches on top and share them soon.

Paolo Abeni (9):
  mptcp: refactor passive socket initialization.
  mptcp: drop unneeded argument
  mptcp: drop legacy code.
  mptcp: avoid unneeded __mptcp_nmpc_socket() usage
  mptcp: move fastopen subflow check inside mptcp_sendmsg_fastopen()
  mptcp: move first subflow allocation at mpc access time
  mptcp: do not keep around the first subflow after disconnect.
  mptcp: fastclose msk when cleaning unaccepted sockets
  mptcp: refactor mptcp_stream_accept()

 net/mptcp/options.c    |   9 +--
 net/mptcp/pm.c         |   4 +-
 net/mptcp/pm_netlink.c |   4 +-
 net/mptcp/protocol.c   | 159 ++++++++++++++++++++++-------------------
 net/mptcp/protocol.h   |   4 +-
 net/mptcp/sockopt.c    |  18 ++---
 net/mptcp/subflow.c    |  40 +++++++----
 7 files changed, 132 insertions(+), 106 deletions(-)

-- 
2.38.1


             reply	other threads:[~2023-01-13 18:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13 18:20 Paolo Abeni [this message]
2023-01-13 18:20 ` [PATCH mptcp-next 1/9] mptcp: refactor passive socket initialization Paolo Abeni
2023-01-13 18:20 ` [PATCH mptcp-next 2/9] mptcp: drop unneeded argument Paolo Abeni
2023-01-13 18:20 ` [PATCH mptcp-next 3/9] mptcp: drop legacy code Paolo Abeni
2023-01-13 18:20 ` [PATCH mptcp-next 4/9] mptcp: avoid unneeded __mptcp_nmpc_socket() usage Paolo Abeni
2023-01-13 18:20 ` [PATCH mptcp-next 5/9] mptcp: move fastopen subflow check inside mptcp_sendmsg_fastopen() Paolo Abeni
2023-01-13 18:20 ` [PATCH mptcp-next 6/9] mptcp: move first subflow allocation at mpc access time Paolo Abeni
2023-01-16 18:32   ` Paolo Abeni
2023-01-13 18:20 ` [PATCH mptcp-next 7/9] mptcp: do not keep around the first subflow after disconnect Paolo Abeni
2023-01-13 18:20 ` [PATCH mptcp-next 8/9] mptcp: fastclose msk when cleaning unaccepted sockets Paolo Abeni
2023-01-13 18:20 ` [PATCH mptcp-next 9/9] mptcp: refactor mptcp_stream_accept() Paolo Abeni
2023-01-13 19:28   ` mptcp: refactor mptcp_stream_accept(): Tests Results MPTCP CI

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.1673629755.git.pabeni@redhat.com \
    --to=pabeni@redhat.com \
    --cc=mptcp@lists.linux.dev \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox