From patchwork Thu Nov  5 17:01:21 2020
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Patchwork-Submitter: Florian Westphal <fw@strlen.de>
X-Patchwork-Id: 1395129
Return-Path: <mptcp-bounces@lists.01.org>
X-Original-To: incoming@patchwork.ozlabs.org
Delivered-To: patchwork-incoming@bilbo.ozlabs.org
Authentication-Results: ozlabs.org;
 spf=none (no SPF record) smtp.mailfrom=lists.01.org (client-ip=198.145.21.10;
 helo=ml01.01.org; envelope-from=mptcp-bounces@lists.01.org;
 receiver=<UNKNOWN>)
Authentication-Results: ozlabs.org;
 dmarc=none (p=none dis=none) header.from=strlen.de
Received: from ml01.01.org (ml01.01.org [198.145.21.10])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest
 SHA256)
	(No client certificate requested)
	by ozlabs.org (Postfix) with ESMTPS id 4CRqYg2xdyz9sRK
	for <incoming@patchwork.ozlabs.org>; Fri,  6 Nov 2020 04:01:42 +1100 (AEDT)
Received: from ml01.vlan13.01.org (localhost [IPv6:::1])
	by ml01.01.org (Postfix) with ESMTP id 0AFC916646E2B;
	Thu,  5 Nov 2020 09:01:39 -0800 (PST)
Received-SPF: Pass (mailfrom) identity=mailfrom;
 client-ip=2a0a:51c0:0:12e:520::1; helo=chamillionaire.breakpoint.cc;
 envelope-from=fw@breakpoint.cc; receiver=<UNKNOWN>
Received: from Chamillionaire.breakpoint.cc (Chamillionaire.breakpoint.cc
 [IPv6:2a0a:51c0:0:12e:520::1])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	(No client certificate requested)
	by ml01.01.org (Postfix) with ESMTPS id 54D2616646E26
	for <mptcp@lists.01.org>; Thu,  5 Nov 2020 09:01:37 -0800 (PST)
Received: from fw by Chamillionaire.breakpoint.cc with local (Exim 4.92)
	(envelope-from <fw@breakpoint.cc>)
	id 1kaidg-0007Cf-Uz; Thu, 05 Nov 2020 18:01:33 +0100
From: Florian Westphal <fw@strlen.de>
To: <mptcp@lists.01.org>
Date: Thu,  5 Nov 2020 18:01:21 +0100
Message-Id: <20201105170126.5627-1-fw@strlen.de>
X-Mailer: git-send-email 2.26.2
MIME-Version: 1.0
Message-ID-Hash: 7KWYACTACPYSBRHMEEFY27YBY6Q4TDEM
X-Message-ID-Hash: 7KWYACTACPYSBRHMEEFY27YBY6Q4TDEM
X-MailFrom: fw@breakpoint.cc
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency;
 loop; banned-address; member-moderation; nonmember-moderation; administrivia;
 implicit-dest; max-recipients; max-size; news-moderation; no-subject;
 suspicious-header
X-Mailman-Version: 3.1.1
Precedence: list
Subject: [MPTCP] [PATCH MPTCP 0/5] mptcp: add reset and fastclose option
 support
List-Id: Discussions regarding MPTCP upstreaming <mptcp.lists.01.org>
Archived-At: 
 <https://lists.01.org/hyperkitty/list/mptcp@lists.01.org/message/7KWYACTACPYSBRHMEEFY27YBY6Q4TDEM/>
List-Archive: <https://lists.01.org/hyperkitty/list/mptcp@lists.01.org/>
List-Help: <mailto:mptcp-request@lists.01.org?subject=help>
List-Post: <mailto:mptcp@lists.01.org>
List-Subscribe: <mailto:mptcp-join@lists.01.org>
List-Unsubscribe: <mailto:mptcp-leave@lists.01.org>

This series adds reset and fast close options.
Both need common infrastructure:
 1. need to parse mptcp option in tcp reset packets, and making
    them available to the stack
 2. ability to add mptcp option to tcp reset packets

First two patches move code around and add mptcp-callsite for
option deciding from rst packets.

Patch 3 adds reset support (both decoding and adding them).
Patch 4 adds the fastclose receive processing.
Patch 5 sends a fastclose packet when userspace calls close()
while there is unread data in the mptcp rx queue.

Patch 2) is not strictly need ATM, I could rework the series
to remove it and only handle fastclose for the time being.
Last patch could be removed as well so we only handle the rx case
(there is nothing in RFC that says we must send fastclose).

Comments welcome.