From: Paolo Abeni <pabeni@redhat.com>
To: mptcp@lists.linux.dev
Subject: [PATCH v3 mptcp-net 0/3] mptcp: cg and backlog follow-up
Date: Thu, 13 Nov 2025 01:10:49 +0100 [thread overview]
Message-ID: <cover.1762992570.git.pabeni@redhat.com> (raw)
This is a v2 of:
https://lore.kernel.org/mptcp/ed5c5ea1de503f6dc8a514b5eb4c9d16c431646f.1762696333.git.pabeni@redhat.com/
It turns out the previous revision was prone to a lot of ugly race.
Addressing them needs a some pre-reqs.
Races are due to MPJ subflows racing with accept() and possibly adding
non accounted memory to the backlog while the account code is trying to
handle backlog_len.
Paolo Abeni (3):
mptcp: fix grafting corner case
Squash-to: "mptcp: fix memcg accounting for passive sockets"
Squash-to: "mptcp: leverage the backlog for RX packet processing"
net/mptcp/protocol.c | 104 +++++++++++++++++++++++++++++++++++--------
net/mptcp/protocol.h | 1 +
2 files changed, 87 insertions(+), 18 deletions(-)
--
2.51.1
next reply other threads:[~2025-11-13 0:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 0:10 Paolo Abeni [this message]
2025-11-13 0:10 ` [PATCH v3 mptcp-net 1/3] mptcp: fix grafting corner case Paolo Abeni
2025-11-13 8:47 ` Matthieu Baerts
2025-11-13 17:09 ` Paolo Abeni
2025-11-13 17:14 ` Matthieu Baerts
2025-11-13 0:10 ` [PATCH v3 mptcp-net 2/3] Squash-to: "mptcp: fix memcg accounting for passive sockets" Paolo Abeni
2025-11-13 0:10 ` [PATCH v3 mptcp-net 3/3] Squash-to: "mptcp: leverage the backlog for RX packet processing" Paolo Abeni
2025-11-13 9:00 ` Matthieu Baerts
2025-11-13 11:30 ` kernel test robot
2025-11-13 17:16 ` Matthieu Baerts
2025-11-13 11:52 ` kernel test robot
2025-11-13 0:35 ` [PATCH v3 mptcp-net 0/3] mptcp: cg and backlog follow-up MPTCP CI
2025-11-13 1:21 ` MPTCP CI
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=cover.1762992570.git.pabeni@redhat.com \
--to=pabeni@redhat.com \
--cc=mptcp@lists.linux.dev \
/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.