From: Matthieu Baerts <matthieu.baerts@tessares.net>
To: Florian Westphal <fw@strlen.de>, Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v2 00/10] mptcp: add SOL_SOCKET support
Date: Wed, 14 Apr 2021 18:07:09 +0200 [thread overview]
Message-ID: <e0e79a1e-537f-632b-1157-e25e70bd817e@tessares.net> (raw)
In-Reply-To: <20210413155447.14043-1-fw@strlen.de>
Hi Florian, Paolo,
On 13/04/2021 17:54, Florian Westphal wrote:
> This patch set improves support for several SOL_SOCKET tuneables,
> addressing comments received for v1 patch set.
>
> Changes since v1:
> - In patch 1, move addition of a variable to patch 2 (Paolo)
> - In patch 2, restrict overflow of sequence count to lower 24 bits (Mat)
> - In patch 2, remove a obsolete check on msk->setsockopt_check (Paolo)
Thank you for the patches and the reviews!
Just applied in our tree with Paolo's Acked-by tags and a small conflict
resolution:
- 6a63626d8b65: mptcp: add skeleton to sync msk socket options to subflows
- 8d64e3af6a01: mptcp: tag sequence_seq with socket state
- d3123e0f11d5: mptcp: setsockopt: handle SO_KEEPALIVE and SO_PRIORITY
- 312dafe0427f: mptcp: setsockopt: handle receive/send buffer and device
bind
- 0c26e2e19d8c: mptcp: setsockopt: support SO_LINGER
- 796f06044fcd: mptcp: setsockopt: add SO_MARK support
- 5380a8b59dd4: mptcp: setsockopt: add SO_INCOMING_CPU
- 56063458e089: mptcp: setsockopt: SO_DEBUG and no-op options
- a403361b4aca: mptcp: sockopt: add TCP_CONGESTION and TCP_INFO
- 2857df86a4b9: selftests: mptcp: add packet mark test case
- 0d4cddd31dc4: conflict in t/DO-NOT-MERGE-mptcp-use-kmalloc-on-kasan-build
- Results: f90b3d445732..f15eff9346bc
Export + builds are in progress!
Cheers,
Matt
--
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net
prev parent reply other threads:[~2021-04-14 16:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 15:54 [PATCH mptcp-next v2 00/10] mptcp: add SOL_SOCKET support Florian Westphal
2021-04-13 15:54 ` [PATCH mptcp-next v2 01/10] mptcp: add skeleton to sync msk socket options to subflows Florian Westphal
2021-04-13 15:54 ` [PATCH mptcp-next v2 02/10] mptcp: tag sequence_seq with socket state Florian Westphal
2021-04-13 15:54 ` [PATCH mptcp-next v2 03/10] mptcp: setsockopt: handle SO_KEEPALIVE and SO_PRIORITY Florian Westphal
2021-04-13 15:54 ` [PATCH mptcp-next v2 04/10] mptcp: setsockopt: handle receive/send buffer and device bind Florian Westphal
2021-04-13 15:54 ` [PATCH mptcp-next v2 05/10] mptcp: setsockopt: support SO_LINGER Florian Westphal
2021-04-13 15:54 ` [PATCH mptcp-next v2 06/10] mptcp: setsockopt: add SO_MARK support Florian Westphal
2021-04-13 15:54 ` [PATCH mptcp-next v2 07/10] mptcp: setsockopt: add SO_INCOMING_CPU Florian Westphal
2021-04-13 15:54 ` [PATCH mptcp-next v2 08/10] mptcp: setsockopt: SO_DEBUG and no-op options Florian Westphal
2021-04-13 15:54 ` [PATCH mptcp-next v2 09/10] mptcp: sockopt: add TCP_CONGESTION and TCP_INFO Florian Westphal
2021-04-13 15:54 ` [PATCH mptcp-next v2 10/10] selftests: mptcp: add packet mark test case Florian Westphal
2021-04-13 16:30 ` [PATCH mptcp-next v2 00/10] mptcp: add SOL_SOCKET support Paolo Abeni
2021-04-14 16:07 ` Matthieu Baerts [this message]
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=e0e79a1e-537f-632b-1157-e25e70bd817e@tessares.net \
--to=matthieu.baerts@tessares.net \
--cc=fw@strlen.de \
--cc=mptcp@lists.linux.dev \
--cc=pabeni@redhat.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 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).