From: Jakub Kicinski <kuba@kernel.org>
To: Geliang Tang <geliang@kernel.org>
Cc: Matthieu Baerts <matttbe@kernel.org>,
Mat Martineau <martineau@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Neal Cardwell <ncardwell@google.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
John Fastabend <john.fastabend@gmail.com>,
Sabrina Dubroca <sd@queasysnail.net>,
Hannes Reinecke <hare@suse.de>,
Geliang Tang <tanggeliang@kylinos.cn>,
netdev@vger.kernel.org, mptcp@lists.linux.dev,
Gang Yan <yangang@kylinos.cn>, Zqiang <qiang.zhang@linux.dev>
Subject: Re: [RFC net-next 00/17] MPTCP KTLS support
Date: Mon, 22 Jun 2026 09:00:59 -0700 [thread overview]
Message-ID: <20260622090059.5d1813dd@kernel.org> (raw)
In-Reply-To: <cover.1782123118.git.tanggeliang@kylinos.cn>
On Mon, 22 Jun 2026 18:43:20 +0800 Geliang Tang wrote:
> Subject: [RFC net-next 00/17] MPTCP KTLS support
Please no. We have a ton of unfixed bugs and may have to revert some of
the features we dropped back in. I'd prefer to avoid large new bug
surfaces until we reach an LTS release.
prev parent reply other threads:[~2026-06-22 16:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 10:43 [RFC net-next 00/17] MPTCP KTLS support Geliang Tang
2026-06-22 10:43 ` [RFC net-next 01/17] tls: make tls_ctx_create and update_sk_prot static Geliang Tang
2026-06-22 10:43 ` [RFC net-next 02/17] tls: factor out __tls_build_proto for mptcp support Geliang Tang
2026-06-22 10:43 ` [RFC net-next 03/17] tls: add protocol dimension to tls operation cache Geliang Tang
2026-06-22 10:43 ` [RFC net-next 04/17] mptcp: add sendmsg_locked to proto_ops Geliang Tang
2026-06-22 10:43 ` [RFC net-next 05/17] tls: use sendmsg_locked from the underlying socket Geliang Tang
2026-06-22 10:43 ` [RFC net-next 06/17] mptcp: implement peek_len for proto_ops Geliang Tang
2026-06-22 10:43 ` [RFC net-next 07/17] tls: replace tcp_inq with socket peek_len Geliang Tang
2026-06-22 10:43 ` [RFC net-next 08/17] tls: store original read_sock for non-tcp sockets Geliang Tang
2026-06-22 10:43 ` [RFC net-next 09/17] tls: introduce tls protocol ops structure Geliang Tang
2026-06-22 10:43 ` [RFC net-next 10/17] tls: use protocol ops via tls_context Geliang Tang
2026-06-22 10:43 ` [RFC net-next 11/17] mptcp: implement mptcp-specific tls protocol ops Geliang Tang
2026-06-22 10:43 ` [RFC net-next 12/17] tls: add mptcp support for sk_poll Geliang Tang
2026-06-22 10:43 ` [RFC net-next 13/17] tls: disable device offload for mptcp sockets Geliang Tang
2026-06-22 10:43 ` [RFC net-next 14/17] mptcp: update mptcp_check_readable helper Geliang Tang
2026-06-22 10:43 ` [RFC net-next 15/17] mptcp: implement ulp getsockopt for tls support Geliang Tang
2026-06-22 10:43 ` [RFC net-next 16/17] mptcp: implement ulp setsockopt " Geliang Tang
2026-06-22 10:43 ` [RFC net-next 17/17] selftests: mptcp: connect: use espintcp for ulp test Geliang Tang
2026-06-22 16:00 ` Jakub Kicinski [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=20260622090059.5d1813dd@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=hare@suse.de \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuniyu@google.com \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qiang.zhang@linux.dev \
--cc=sd@queasysnail.net \
--cc=tanggeliang@kylinos.cn \
--cc=yangang@kylinos.cn \
/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