From: Matthieu Baerts <matttbe@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Gang Yan <yangang@kylinos.cn>
Cc: patches@lists.linux.dev, Paolo Abeni <pabeni@redhat.com>,
stable@vger.kernel.org, MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: [PATCH 6.18 214/275] mptcp: sync the msk->sndbuf at accept() time
Date: Tue, 5 May 2026 19:50:47 +0200 [thread overview]
Message-ID: <68c8f2a7-6149-4b65-bb1b-0ab4cd4067cf@kernel.org> (raw)
In-Reply-To: <1bbeee9b-b69b-4be9-84ee-ddadda4793ef@kernel.org>
On 05/05/2026 19:16, Matthieu Baerts wrote:
> Hi Greg, Gang,
>
> On 04/05/2026 15:52, Greg Kroah-Hartman wrote:
>> 6.18-stable review patch. If anyone has any objections, please let me know.
>
> Please drop this patch, it looks like it is introducing regressions on
> v6.18:
(...)
> @Gang: could you eventually have a look, please?
FYI, I quickly checked, and I noticed that 'subflow' is different on
v6.18 due to the "mptcp_for_each_subflow(msk, subflow)" removed in
68c7c3867145 ("mptcp: fix memcg accounting for passive sockets").
Moving __mptcp_propagate_sndbuf() a couple of lines above, before the
for-loop, should fix the issue. I can eventually look at sending a patch
with the fix.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2026-05-05 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260504135142.929052779@linuxfoundation.org>
[not found] ` <20260504135151.022829547@linuxfoundation.org>
2026-05-05 17:16 ` [PATCH 6.18 214/275] mptcp: sync the msk->sndbuf at accept() time Matthieu Baerts
2026-05-05 17:50 ` Matthieu Baerts [this message]
2026-05-05 20:41 ` Sasha Levin
2026-05-06 1:47 ` gang.yan
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=68c8f2a7-6149-4b65-bb1b-0ab4cd4067cf@kernel.org \
--to=matttbe@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=mptcp@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=patches@lists.linux.dev \
--cc=stable@vger.kernel.org \
--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