From: Stefano Brivio <sbrivio@redhat.com>
To: Simon Baatz via B4 Relay <devnull+gmbnomis.gmail.com@kernel.org>
Cc: gmbnomis@gmail.com, Eric Dumazet <edumazet@google.com>,
Neal Cardwell <ncardwell@google.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
David Ahern <dsahern@kernel.org>, Jon Maloy <jmaloy@redhat.com>,
Jason Xing <kerneljasonxing@gmail.com>,
mfreemon@cloudflare.com, Shuah Khan <shuah@kernel.org>,
Matthieu Baerts <matttbe@kernel.org>,
Mat Martineau <martineau@kernel.org>,
Geliang Tang <geliang@kernel.org>,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
mptcp@lists.linux.dev
Subject: Re: [PATCH net-next v3 1/6] tcp: implement RFC 7323 window retraction receiver requirements
Date: Tue, 10 Mar 2026 09:58:07 +0100 (CET) [thread overview]
Message-ID: <20260310095806.121d198f@elisabeth> (raw)
In-Reply-To: <20260309-tcp_rfc7323_retract_wnd_rfc-v3-1-4c7f96b1ec69@gmail.com>
Simon,
On Mon, 09 Mar 2026 09:02:26 +0100
Simon Baatz via B4 Relay <devnull+gmbnomis.gmail.com@kernel.org> wrote:
> [...]
>
> diff --git a/include/linux/tcp.h b/include/linux/tcp.h
> index f72eef31fa23cc584f2f0cefacdc35cae43aa52d..73aa2e0ccd1d7a6314a00c27950b019b62a3851c 100644
> --- a/include/linux/tcp.h
> +++ b/include/linux/tcp.h
> @@ -316,6 +316,9 @@ struct tcp_sock {
> */
> u32 app_limited; /* limited until "delivered" reaches this val */
> u32 rcv_wnd; /* Current receiver window */
> + u32 rcv_mwnd_seq; /* Maximum window sequence number (RFC 7323,
> + * section 2.4, receiver requirements)
> + */
I didn't follow the rest of the discussion but, at this point, what
does this mean for applications (CRIU, passt) dumping/restoring socket
data? Do they have to adapt? I couldn't find this bit of information
anywhere in v3.
--
Stefano
next prev parent reply other threads:[~2026-03-10 8:58 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 8:02 [PATCH net-next v3 0/6] tcp: RFC 7323-compliant window retraction handling Simon Baatz
2026-03-09 8:02 ` Simon Baatz via B4 Relay
2026-03-09 8:02 ` [PATCH net-next v3 1/6] tcp: implement RFC 7323 window retraction receiver requirements Simon Baatz
2026-03-09 8:02 ` Simon Baatz via B4 Relay
2026-03-09 9:22 ` Eric Dumazet
2026-03-09 18:35 ` Simon Baatz
2026-03-10 7:40 ` Eric Dumazet
2026-03-10 8:58 ` Stefano Brivio [this message]
2026-03-10 22:34 ` Simon Baatz
2026-03-09 8:02 ` [PATCH net-next v3 2/6] mptcp: keep rcv_mwnd_seq in sync with subflow rcv_wnd Simon Baatz
2026-03-09 8:02 ` Simon Baatz via B4 Relay
2026-03-10 8:46 ` Eric Dumazet
2026-03-11 18:27 ` Matthieu Baerts
2026-03-11 22:08 ` Simon Baatz
2026-03-12 11:01 ` Matthieu Baerts
2026-03-09 8:02 ` [PATCH net-next v3 3/6] tcp: increase LINUX_MIB_BEYOND_WINDOW for SKB_DROP_REASON_TCP_OVERWINDOW Simon Baatz
2026-03-09 8:02 ` Simon Baatz via B4 Relay
2026-03-09 9:27 ` Eric Dumazet
2026-03-09 8:02 ` [PATCH net-next v3 4/6] selftests/net: packetdrill: add tcp_rcv_wnd_shrink_nomem.pkt Simon Baatz
2026-03-09 8:02 ` Simon Baatz via B4 Relay
2026-03-10 8:46 ` Eric Dumazet
2026-03-09 8:02 ` [PATCH net-next v3 5/6] selftests/net: packetdrill: add tcp_rcv_wnd_shrink_allowed.pkt Simon Baatz
2026-03-09 8:02 ` Simon Baatz via B4 Relay
2026-03-10 8:52 ` Eric Dumazet
2026-03-09 8:02 ` [PATCH net-next v3 6/6] selftests/net: packetdrill: add tcp_rcv_neg_window.pkt Simon Baatz
2026-03-09 8:02 ` Simon Baatz via B4 Relay
2026-03-10 8:54 ` Eric Dumazet
2026-03-10 23:09 ` Simon Baatz
2026-03-14 3:58 ` Eric Dumazet
2026-03-14 14:55 ` Eric Dumazet
2026-03-14 15:01 ` Jakub Kicinski
2026-03-14 17:07 ` Simon Baatz
2026-03-16 21:51 ` Simon Baatz
2026-03-09 9:34 ` [PATCH net-next v3 0/6] tcp: RFC 7323-compliant window retraction handling MPTCP CI
2026-03-14 15:40 ` patchwork-bot+netdevbpf
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=20260310095806.121d198f@elisabeth \
--to=sbrivio@redhat.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=devnull+gmbnomis.gmail.com@kernel.org \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=gmbnomis@gmail.com \
--cc=horms@kernel.org \
--cc=jmaloy@redhat.com \
--cc=kerneljasonxing@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mfreemon@cloudflare.com \
--cc=mptcp@lists.linux.dev \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.