netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: netdev@vger.kernel.org
Cc: Eric Dumazet <edumazet@google.com>,
	"David S . Miller" <davem@davemloft.net>,
	Christoph Paasch <cpaasch@apple.com>
Subject: [PATCH net-next 0/3] mptcp: fix MP_JOIN failure handling
Date: Wed, 13 May 2020 17:31:01 +0200	[thread overview]
Message-ID: <cover.1589383730.git.pabeni@redhat.com> (raw)

Currently if we hit an MP_JOIN failure on the third ack, the child socket is
closed with reset, but the request socket is not deleted, causing weird
behaviors.

The main problem is that MPTCP's MP_JOIN code needs to plug it's own
'valid 3rd ack' checks and the current TCP callbacks do not allow that.

This series tries to address the above shortcoming introducing a new MPTCP
specific bit in a 'struct tcp_request_sock' hole, and leveraging that to allow
tcp_check_req releasing the request socket when needed.

The above allows cleaning-up a bit current MPTCP hooking in tcp_check_req().

An alternative solution, possibly cleaner but more invasive, would be
changing the 'bool *own_req' syn_recv_sock() argument into 'int *req_status'
and let MPTCP set it to 'REQ_DROP'.

RFC -> v1:
 - move the drop_req bit inside tcp_request_sock (Eric)

Paolo Abeni (3):
  mptcp: add new sock flag to deal with join subflows
  inet_connection_sock: factor out destroy helper.
  mptcp: cope better with MP_JOIN failure

 include/linux/tcp.h                |  3 +++
 include/net/inet_connection_sock.h |  8 ++++++++
 include/net/mptcp.h                | 17 ++++++++++-------
 net/ipv4/inet_connection_sock.c    |  6 +-----
 net/ipv4/tcp_minisocks.c           |  2 +-
 net/mptcp/protocol.c               |  7 -------
 net/mptcp/subflow.c                | 17 +++++++++++------
 7 files changed, 34 insertions(+), 26 deletions(-)

-- 
2.21.3


             reply	other threads:[~2020-05-13 15:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 15:31 Paolo Abeni [this message]
2020-05-13 15:31 ` [PATCH net-next 1/3] mptcp: add new sock flag to deal with join subflows Paolo Abeni
2020-05-14 20:13   ` Mat Martineau
2020-05-15  9:15     ` Paolo Abeni
2020-05-15 15:52     ` Paolo Abeni
2020-05-13 15:31 ` [PATCH net-next 2/3] inet_connection_sock: factor out destroy helper Paolo Abeni
2020-05-13 15:31 ` [PATCH net-next 3/3] mptcp: cope better with MP_JOIN failure Paolo Abeni
2020-05-13 17:07 ` [PATCH net-next 0/3] mptcp: fix MP_JOIN failure handling Christoph Paasch
2020-05-14 22:19 ` David Miller

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.1589383730.git.pabeni@redhat.com \
    --to=pabeni@redhat.com \
    --cc=cpaasch@apple.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=netdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).