* [PATCH net 0/3] tcp, mptcp: fix receive buffer sizing and peek accounting
@ 2026-11-17 5:22 lei lei
2026-11-17 5:22 ` [PATCH net 1/3] tcp: saturate window-to-memory conversions at INT_MAX lei lei
` (3 more replies)
0 siblings, 4 replies; 8+ messages in thread
From: lei lei @ 2026-11-17 5:22 UTC (permalink / raw)
To: netdev@vger.kernel.org
Cc: mptcp@lists.linux.dev, edumazet@kernel.org, ncardwell@google.com,
kuniyu@google.com, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, matttbe@kernel.org,
martineau@kernel.org, geliang@kernel.org
This series fixes receive-buffer sizing and accounting errors in TCP
and MPTCP.
The first two patches prevent integer truncation from producing an
undersized receive-memory budget. __tcp_space_from_win() can return a
truncated int, while tcp_rcvbuf_grow() and mptcp_rcvbuf_grow() can wrap
a u32 window prediction. The fixes saturate the conversion result at
INT_MAX and keep growth predictions in u64 until they are bounded for
the existing helper interface. Patch 2 depends on patch 1.
The third patch restores the MSG_PEEK exclusion from MPTCP receive
autotuning. Repeated peeks currently count the same queued bytes as
application consumption, which can inflate the receive-memory budget
without the application draining the queue.
Validation used targeted IPv4 loopback socket tests on unpatched and
patched kernels in x86_64 QEMU/KVM guests. GCC 13.3 builds completed
without warnings. The tests confirmed that, with the fixes applied:
- Large SO_RCVLOWAT settings on TCP and MPTCP correctly increase the
receive-memory budget to INT_MAX when tcp_rmem[2] is INT_MAX and
the window-to-memory conversion exceeds the representable range.
- For queued bursts whose predicted window exceeds 32 bits, TCP and
MPTCP receive budgets now reach the configured 64 MiB limit.
- Repeated MSG_PEEK calls leave both a fixed 32 KiB MPTCP receive
queue and its memory budget unchanged. A subsequent consuming read
returns the original data intact.
The investigation began with sk_rcvbuf failing to grow despite
application reads during normal use, constraining the advertised
receive window.
OpenAI Codex assisted with designing trigger conditions and socket
tests for reproduction and validation.
lllei (3):
tcp: saturate window-to-memory conversions at INT_MAX
net: bound receive window predictions before narrowing
mptcp: exclude MSG_PEEK from receive buffer autotuning
include/net/tcp.h | 2 +-
net/ipv4/tcp_input.c | 11 ++++++-----
net/mptcp/protocol.c | 12 +++++++-----
3 files changed, 14 insertions(+), 11 deletions(-)
base-commit: aa40afa831ebfe45e40a23721711059f2ac584d4
--
2.43.0
^ permalink raw reply [flat|nested] 8+ messages in thread
* [PATCH net 1/3] tcp: saturate window-to-memory conversions at INT_MAX
2026-11-17 5:22 [PATCH net 0/3] tcp, mptcp: fix receive buffer sizing and peek accounting lei lei
@ 2026-11-17 5:22 ` lei lei
2026-11-18 5:22 ` sashiko-bot
2026-11-17 5:22 ` [PATCH net 2/3] net: bound receive window predictions before narrowing lei lei
` (2 subsequent siblings)
3 siblings, 1 reply; 8+ messages in thread
From: lei lei @ 2026-11-17 5:22 UTC (permalink / raw)
To: netdev@vger.kernel.org
Cc: mptcp@lists.linux.dev, edumazet@kernel.org, ncardwell@google.com,
kuniyu@google.com, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, matttbe@kernel.org,
martineau@kernel.org, geliang@kernel.org
__tcp_space_from_win() computes a receive-memory requirement in u64 but
returns int. A result above INT_MAX can therefore become negative or
wrap to a smaller positive value before the caller compares or limits it.
TCP and MPTCP SO_RCVLOWAT handling compare this result with sk_rcvbuf.
They can accept a large low watermark without increasing the receive
budget because the truncated requirement appears smaller than the
existing buffer. Receive autotuning uses the same conversion helper.
Saturate the u64 result at INT_MAX before returning it. This matches the
int type of sk_rcvbuf and preserves the value and rounding of every
representable result.
TCP and MPTCP loopback tests with tcp_rmem[2]=INT_MAX and
SO_RCVLOWAT=INT_MAX/2 reproduce the missed update after learning a
scaling ratio below 128. With this change, both budgets reach INT_MAX.
Fixes: dfa2f0483360 ("tcp: get rid of sysctl_tcp_adv_win_scale")
Signed-off-by: lllei <llleigoing@outlook.com>
---
include/net/tcp.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/net/tcp.h b/include/net/tcp.h
index 5c9203aae..09827f1ae 100644
--- a/include/net/tcp.h
+++ b/include/net/tcp.h
@@ -1799,7 +1799,7 @@ static inline int __tcp_space_from_win(u8 scaling_ratio, int win)
u64 val = (u64)win << TCP_RMEM_TO_WIN_SCALE;
do_div(val, scaling_ratio);
- return val;
+ return min_t(u64, val, INT_MAX);
}
static inline int tcp_space_from_win(const struct sock *sk, int win)
--
2.43.0
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [PATCH net 2/3] net: bound receive window predictions before narrowing
2026-11-17 5:22 [PATCH net 0/3] tcp, mptcp: fix receive buffer sizing and peek accounting lei lei
2026-11-17 5:22 ` [PATCH net 1/3] tcp: saturate window-to-memory conversions at INT_MAX lei lei
@ 2026-11-17 5:22 ` lei lei
2026-11-18 5:22 ` sashiko-bot
2026-11-17 5:22 ` [PATCH net 3/3] mptcp: exclude MSG_PEEK from receive buffer autotuning lei lei
2026-11-17 7:04 ` [PATCH net 0/3] tcp, mptcp: fix receive buffer sizing and peek accounting MPTCP CI
3 siblings, 1 reply; 8+ messages in thread
From: lei lei @ 2026-11-17 5:22 UTC (permalink / raw)
To: netdev@vger.kernel.org
Cc: mptcp@lists.linux.dev, edumazet@kernel.org, ncardwell@google.com,
kuniyu@google.com, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, matttbe@kernel.org,
martineau@kernel.org, geliang@kernel.org
tcp_rcvbuf_grow() and mptcp_rcvbuf_grow() compute growth terms in u64 but
accumulate the predicted receive window in u32. The prediction can wrap
before conversion to a memory budget and application of tcp_rmem[2].
For example, oldval=16 KiB and newval=4104 KiB produce a slow-start
window prediction of 4 GiB + 8 MiB. Storing it in u32 leaves only 8 MiB,
so the memory limit is applied to an already truncated prediction.
Keep rcvwin in u64 and promote newval before the initial shift. Clamp
the completed prediction at INT_MAX before passing it to the existing
int-input window-to-memory helpers. Since scaling_ratio is a nonzero
u8, the required memory is at least as large as the window. Predictions
above INT_MAX therefore already require a saturated receive budget.
The helpers' return saturation and the existing tcp_rmem[2] limit then
provide the appropriate memory bound.
TCP and MPTCP loopback tests using small warm-up reads followed by a
queued burst of about 4 MiB previously left the budget below the
configured 64 MiB limit. With this change, both reach that limit.
Fixes: aa251c84636c ("tcp: fix too slow tcp_rcvbuf_grow() action")
Signed-off-by: lllei <llleigoing@outlook.com>
---
net/ipv4/tcp_input.c | 11 ++++++-----
net/mptcp/protocol.c | 9 +++++----
2 files changed, 11 insertions(+), 9 deletions(-)
diff --git a/net/ipv4/tcp_input.c b/net/ipv4/tcp_input.c
index a2074a1af..6d5950dbe 100644
--- a/net/ipv4/tcp_input.c
+++ b/net/ipv4/tcp_input.c
@@ -940,9 +940,9 @@ void tcp_rcvbuf_grow(struct sock *sk, u32 newval)
{
const struct net *net = sock_net(sk);
struct tcp_sock *tp = tcp_sk(sk);
- u32 rcvwin, rcvbuf, cap, oldval;
+ u32 rcvbuf, cap, oldval;
u32 rtt_threshold, rtt_us;
- u64 grow;
+ u64 rcvwin, grow;
oldval = tp->rcvq_space.space;
tp->rcvq_space.space = newval;
@@ -952,7 +952,7 @@ void tcp_rcvbuf_grow(struct sock *sk, u32 newval)
return;
/* DRS is always one RTT late. */
- rcvwin = newval << 1;
+ rcvwin = (u64)newval << 1;
rtt_us = tp->rcv_rtt_est.rtt_us >> 3;
rtt_threshold = READ_ONCE(net->ipv4.sysctl_tcp_rcvbuf_low_rtt);
@@ -961,10 +961,10 @@ void tcp_rcvbuf_grow(struct sock *sk, u32 newval)
* It might take few additional ms to reach 'line rate',
* but will avoid sk_rcvbuf inflation and poor cache use.
*/
- grow = div_u64((u64)rcvwin * rtt_us, rtt_threshold);
+ grow = div_u64(rcvwin * rtt_us, rtt_threshold);
} else {
/* slow start: allow the sender to double its rate. */
- grow = div_u64(((u64)rcvwin << 1) * (newval - oldval), oldval);
+ grow = div_u64((rcvwin << 1) * (newval - oldval), oldval);
}
rcvwin += grow;
@@ -973,6 +973,7 @@ void tcp_rcvbuf_grow(struct sock *sk, u32 newval)
cap = READ_ONCE(net->ipv4.sysctl_tcp_rmem[2]);
+ rcvwin = min_t(u64, rcvwin, INT_MAX);
rcvbuf = min_t(u32, tcp_space_from_win(sk, rcvwin), cap);
if (rcvbuf > sk->sk_rcvbuf) {
WRITE_ONCE(sk->sk_rcvbuf, rcvbuf);
diff --git a/net/mptcp/protocol.c b/net/mptcp/protocol.c
index 8968db580..b3b979403 100644
--- a/net/mptcp/protocol.c
+++ b/net/mptcp/protocol.c
@@ -216,8 +216,8 @@ static bool mptcp_rcvbuf_grow(struct sock *sk, u32 newval)
{
struct mptcp_sock *msk = mptcp_sk(sk);
const struct net *net = sock_net(sk);
- u32 rcvwin, rcvbuf, cap, oldval;
- u64 grow;
+ u32 rcvbuf, cap, oldval;
+ u64 rcvwin, grow;
oldval = msk->rcvq_space.space;
msk->rcvq_space.space = newval;
@@ -226,15 +226,16 @@ static bool mptcp_rcvbuf_grow(struct sock *sk, u32 newval)
return false;
/* DRS is always one RTT late. */
- rcvwin = newval << 1;
+ rcvwin = (u64)newval << 1;
/* slow start: allow the sender to double its rate. */
- grow = (u64)rcvwin * (newval - oldval);
+ grow = rcvwin * (newval - oldval);
do_div(grow, oldval);
rcvwin += grow << 1;
cap = READ_ONCE(net->ipv4.sysctl_tcp_rmem[2]);
+ rcvwin = min_t(u64, rcvwin, INT_MAX);
rcvbuf = min_t(u32, mptcp_space_from_win(sk, rcvwin), cap);
if (rcvbuf > sk->sk_rcvbuf) {
WRITE_ONCE(sk->sk_rcvbuf, rcvbuf);
--
2.43.0
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [PATCH net 3/3] mptcp: exclude MSG_PEEK from receive buffer autotuning
2026-11-17 5:22 [PATCH net 0/3] tcp, mptcp: fix receive buffer sizing and peek accounting lei lei
2026-11-17 5:22 ` [PATCH net 1/3] tcp: saturate window-to-memory conversions at INT_MAX lei lei
2026-11-17 5:22 ` [PATCH net 2/3] net: bound receive window predictions before narrowing lei lei
@ 2026-11-17 5:22 ` lei lei
2026-11-18 5:22 ` sashiko-bot
2026-11-17 7:04 ` [PATCH net 0/3] tcp, mptcp: fix receive buffer sizing and peek accounting MPTCP CI
3 siblings, 1 reply; 8+ messages in thread
From: lei lei @ 2026-11-17 5:22 UTC (permalink / raw)
To: netdev@vger.kernel.org
Cc: mptcp@lists.linux.dev, edumazet@kernel.org, ncardwell@google.com,
kuniyu@google.com, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, matttbe@kernel.org,
martineau@kernel.org, geliang@kernel.org
__mptcp_recvmsg_mskq() passes bytes copied by MSG_PEEK to
mptcp_rcv_space_adjust(), although those bytes remain in the receive
queue. Repeated peeks count the same data as new application
consumption and can inflate the receive-memory budget. Subtracting the
unread queue at a measurement boundary cannot undo that repeated count.
The receive path originally skipped this adjustment for MSG_PEEK.
Commit 581302298524 ("mptcp: error out earlier on disconnect") moved
the adjustment calls without preserving that check.
Only adjust receive space for non-peeking reads. Keep the returned
byte count unchanged.
A loopback test leaves a fixed 32 KiB queue unread and peeks 4096 times.
Before this change, sk_rcvbuf grows to the configured 8 MiB limit.
Afterwards, both the budget and the queue remain unchanged, and a
subsequent consuming read returns the original data intact.
Fixes: 581302298524 ("mptcp: error out earlier on disconnect")
Signed-off-by: lllei <llleigoing@outlook.com>
---
net/mptcp/protocol.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/net/mptcp/protocol.c b/net/mptcp/protocol.c
index b3b979403..79db8063a 100644
--- a/net/mptcp/protocol.c
+++ b/net/mptcp/protocol.c
@@ -2215,7 +2215,8 @@ static int __mptcp_recvmsg_mskq(struct sock *sk, struct msghdr *msg,
break;
}
- mptcp_rcv_space_adjust(msk, copied);
+ if (!(flags & MSG_PEEK))
+ mptcp_rcv_space_adjust(msk, copied);
return copied;
}
--
2.43.0
^ permalink raw reply related [flat|nested] 8+ messages in thread
* Re: [PATCH net 0/3] tcp, mptcp: fix receive buffer sizing and peek accounting
2026-11-17 5:22 [PATCH net 0/3] tcp, mptcp: fix receive buffer sizing and peek accounting lei lei
` (2 preceding siblings ...)
2026-11-17 5:22 ` [PATCH net 3/3] mptcp: exclude MSG_PEEK from receive buffer autotuning lei lei
@ 2026-11-17 7:04 ` MPTCP CI
3 siblings, 0 replies; 8+ messages in thread
From: MPTCP CI @ 2026-11-17 7:04 UTC (permalink / raw)
To: lei lei; +Cc: mptcp
Hi lei,
Thank you for your modifications, that's great!
Our CI did some validations and here is its report:
- KVM Validation: normal (except selftest_mptcp_join): Unstable: 1 failed test(s): packetdrill_dss ⚠️
- KVM Validation: normal (only selftest_mptcp_join): Success! ✅
- KVM Validation: debug (except selftest_mptcp_join): Success! ✅
- KVM Validation: debug (only selftest_mptcp_join): Success! ✅
- KVM Validation: btf-normal (only bpftest_all): Success! ✅
- KVM Validation: btf-debug (only bpftest_all): Success! ✅
- Perf: Unstable: 1 failed test(s): validation:sched-mem-pressure ⚠️
- Task: https://github.com/multipath-tcp/mptcp_net-next/actions/runs/44024826211
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/64bd1916b1c2
Patchwork: https://patchwork.kernel.org/project/mptcp/list/?series=1213436
If there are some issues, you can reproduce them using the same environment as
the one used by the CI thanks to a docker image, e.g.:
$ cd [kernel source code]
$ docker run -v "${PWD}:${PWD}:rw" -w "${PWD}" --privileged --rm -it \
--pull always mptcp/mptcp-upstream-virtme-docker:latest \
auto-normal
For more details:
https://github.com/multipath-tcp/mptcp-upstream-virtme-docker
Please note that despite all the efforts that have been already done to have a
stable tests suite when executed on a public CI like here, it is possible some
reported issues are not due to your modifications. Still, do not hesitate to
help us improve that ;-)
Cheers,
MPTCP GH Action bot
Bot operated by Matthieu Baerts (NGI0 Core)
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH net 1/3] tcp: saturate window-to-memory conversions at INT_MAX
2026-11-17 5:22 ` [PATCH net 1/3] tcp: saturate window-to-memory conversions at INT_MAX lei lei
@ 2026-11-18 5:22 ` sashiko-bot
0 siblings, 0 replies; 8+ messages in thread
From: sashiko-bot @ 2026-11-18 5:22 UTC (permalink / raw)
To: lei lei; +Cc: mptcp@lists.linux.dev
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [High] tcp: invalid Signed-off-by trailer using handle instead of real
name
--
commit 7ae76d33251cff52d3abaf1bc0db22dbfc70f04d
Author: lei lei <llleigoing@outlook.com>
> tcp: saturate window-to-memory conversions at INT_MAX
>
> __tcp_space_from_win() computes a receive-memory requirement in u64 but
> returns int. A result above INT_MAX can therefore become negative or
> wrap to a smaller positive value before the caller compares or limits it.
>
> TCP and MPTCP SO_RCVLOWAT handling compare this result with sk_rcvbuf.
> They can accept a large low watermark without increasing the receive
> budget because the truncated requirement appears smaller than the
> existing buffer. Receive autotuning uses the same conversion helper.
>
> Saturate the u64 result at INT_MAX before returning it. This matches the
> int type of sk_rcvbuf and preserves the value and rounding of every
> representable result.
>
> TCP and MPTCP loopback tests with tcp_rmem[2]=INT_MAX and
> SO_RCVLOWAT=INT_MAX/2 reproduce the missed update after learning a
> scaling ratio below 128. With this change, both budgets reach INT_MAX.
>
> Fixes: dfa2f0483360 ("tcp: get rid of sysctl_tcp_adv_win_scale")
> Signed-off-by: lllei <llleigoing@outlook.com>
[Severity: High]
The Signed-off-by trailer uses the single-word handle "lllei" instead of a
real human name matching the Author header, which violates Developer's
Certificate of Origin requirements in
Documentation/process/submitting-patches.rst.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261117052200.1507847-1-llleigoing@outlook.com?part=1
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH net 2/3] net: bound receive window predictions before narrowing
2026-11-17 5:22 ` [PATCH net 2/3] net: bound receive window predictions before narrowing lei lei
@ 2026-11-18 5:22 ` sashiko-bot
0 siblings, 0 replies; 8+ messages in thread
From: sashiko-bot @ 2026-11-18 5:22 UTC (permalink / raw)
To: lei lei; +Cc: mptcp@lists.linux.dev
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [High] net: invalid handle and author mismatch in Signed-off-by
trailer
--
commit 0e17123a2c1e28d81f7aa6b0170c8d97f7b356e5
Author: lei lei <llleigoing@outlook.com>
> net: bound receive window predictions before narrowing
>
> tcp_rcvbuf_grow() and mptcp_rcvbuf_grow() compute growth terms in u64 but
> accumulate the predicted receive window in u32. The prediction can wrap
> before conversion to a memory budget and application of tcp_rmem[2].
>
> For example, oldval=16 KiB and newval=4104 KiB produce a slow-start
> window prediction of 4 GiB + 8 MiB. Storing it in u32 leaves only 8 MiB,
> so the memory limit is applied to an already truncated prediction.
>
> Keep rcvwin in u64 and promote newval before the initial shift. Clamp
> the completed prediction at INT_MAX before passing it to the existing
> int-input window-to-memory helpers. Since scaling_ratio is a nonzero
> u8, the required memory is at least as large as the window. Predictions
> above INT_MAX therefore already require a saturated receive budget.
> The helpers' return saturation and the existing tcp_rmem[2] limit then
> provide the appropriate memory bound.
>
> TCP and MPTCP loopback tests using small warm-up reads followed by a
> queued burst of about 4 MiB previously left the budget below the
> configured 64 MiB limit. With this change, both reach that limit.
>
> Fixes: aa251c84636c ("tcp: fix too slow tcp_rcvbuf_grow() action")
> Signed-off-by: lllei <llleigoing@outlook.com>
[Severity: High]
The Signed-off-by trailer uses the single-word handle "lllei" instead of a
real human name and does not match the commit Author header ("lei lei").
Documentation/process/submitting-patches.rst requires a full real name in
Signed-off-by that matches the commit author.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261117052200.1507847-1-llleigoing@outlook.com?part=2
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH net 3/3] mptcp: exclude MSG_PEEK from receive buffer autotuning
2026-11-17 5:22 ` [PATCH net 3/3] mptcp: exclude MSG_PEEK from receive buffer autotuning lei lei
@ 2026-11-18 5:22 ` sashiko-bot
0 siblings, 0 replies; 8+ messages in thread
From: sashiko-bot @ 2026-11-18 5:22 UTC (permalink / raw)
To: lei lei; +Cc: mptcp@lists.linux.dev
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [High] mptcp: invalid Signed-off-by trailer using handle instead of
real name
--
commit bf35feefb3ca938f4410fd363b5311a7fad1ae8f
Author: lei lei <llleigoing@outlook.com>
> mptcp: exclude MSG_PEEK from receive buffer autotuning
>
> __mptcp_recvmsg_mskq() passes bytes copied by MSG_PEEK to
> mptcp_rcv_space_adjust(), although those bytes remain in the receive
> queue. Repeated peeks count the same data as new application
> consumption and can inflate the receive-memory budget. Subtracting the
> unread queue at a measurement boundary cannot undo that repeated count.
>
> The receive path originally skipped this adjustment for MSG_PEEK.
> Commit 581302298524 ("mptcp: error out earlier on disconnect") moved
> the adjustment calls without preserving that check.
>
> Only adjust receive space for non-peeking reads. Keep the returned
> byte count unchanged.
>
> A loopback test leaves a fixed 32 KiB queue unread and peeks 4096 times.
> Before this change, sk_rcvbuf grows to the configured 8 MiB limit.
> Afterwards, both the budget and the queue remain unchanged, and a
> subsequent consuming read returns the original data intact.
>
> Fixes: 581302298524 ("mptcp: error out earlier on disconnect")
> Signed-off-by: lllei <llleigoing@outlook.com>
[Severity: High]
The Signed-off-by trailer uses the single-word handle "lllei" instead of
a real full human name and does not match the commit Author header ("lei
lei"), which violates the Developer's Certificate of Origin requirements
in Documentation/process/submitting-patches.rst.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261117052200.1507847-1-llleigoing@outlook.com?part=3
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2026-11-18 5:22 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-17 5:22 [PATCH net 0/3] tcp, mptcp: fix receive buffer sizing and peek accounting lei lei
2026-11-17 5:22 ` [PATCH net 1/3] tcp: saturate window-to-memory conversions at INT_MAX lei lei
2026-11-18 5:22 ` sashiko-bot
2026-11-17 5:22 ` [PATCH net 2/3] net: bound receive window predictions before narrowing lei lei
2026-11-18 5:22 ` sashiko-bot
2026-11-17 5:22 ` [PATCH net 3/3] mptcp: exclude MSG_PEEK from receive buffer autotuning lei lei
2026-11-18 5:22 ` sashiko-bot
2026-11-17 7:04 ` [PATCH net 0/3] tcp, mptcp: fix receive buffer sizing and peek accounting MPTCP CI
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.