From: Matthieu Baerts <matttbe@kernel.org>
To: MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-net 2/3] mptcp: subflow: no need to copy thmac during ulp_clone
Date: Fri, 21 Aug 2026 08:03:23 +0200 [thread overview]
Message-ID: <ca872631-015b-48d2-a4f3-6803e9a46008@kernel.org> (raw)
In-Reply-To: <20260818-mptcp-cook-reqb-v1-2-052dea9a7f20@kernel.org>
Hello,
On 18/08/2026 19:55, Matthieu Baerts (NGI0) wrote:
> 'thmac' is not used after that point.
>
> Indeed, subflow_ulp_clone() is called when the request on the passive
> side is over, so when the truncated HMAC is no longer needed.
>
> Note that in case of SYN cookies, thmac will not be initialised. So
> better to remove it to avoid a warning for reading uninitialised data.
Note that this modification is harmful in production, and that's why I
didn't add a Fixes tag initially. But it is still important to have it
to prevent warnings about reading uninitialised data. In this case, I
think it is still good to add a Fixes tag not to have reports on stable.
Fixes: 263e1201a2c3 ("mptcp: consolidate synack processing.")
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2026-08-21 6:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 17:55 [PATCH mptcp-net 0/3] mptcp: avoid uninitialised read with MPJ with SYN cookies Matthieu Baerts (NGI0)
2026-08-18 17:55 ` [PATCH mptcp-net 1/3] mptcp: syncookies: remember the request backup flag Matthieu Baerts (NGI0)
2026-08-18 17:55 ` [PATCH mptcp-net 2/3] mptcp: subflow: no need to copy thmac during ulp_clone Matthieu Baerts (NGI0)
2026-08-21 6:03 ` Matthieu Baerts [this message]
2026-08-21 6:06 ` Matthieu Baerts
2026-08-18 17:55 ` [PATCH next mptcp-net 3/3] mptcp: remove thmac from subflow ctx Matthieu Baerts (NGI0)
2026-08-19 9:56 ` Geliang Tang
2026-08-19 10:02 ` Matthieu Baerts
2026-08-21 5:33 ` Geliang Tang
2026-08-18 19:20 ` [PATCH mptcp-net 0/3] mptcp: avoid uninitialised read with MPJ with SYN cookies MPTCP CI
2026-08-21 5:37 ` Geliang Tang
2026-08-21 6:32 ` Matthieu Baerts
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=ca872631-015b-48d2-a4f3-6803e9a46008@kernel.org \
--to=matttbe@kernel.org \
--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.