From: Matthieu Baerts <matttbe@kernel.org>
To: MoYuanhao <moyuanhao3676@163.com>,
edumazet@google.com, davem@davemloft.net, dsahern@kernel.org,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
martineau@kernel.org, geliang@kernel.org,
MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: [PATCH net-next] tcp: Check space before adding MPTCP options
Date: Wed, 4 Dec 2024 12:01:32 +0100 [thread overview]
Message-ID: <80b6603d-ed52-43b7-a434-0253e5de784a@kernel.org> (raw)
In-Reply-To: <20241204085801.11563-1-moyuanhao3676@163.com>
Hi MoYuanhao,
+Cc MPTCP mailing list.
(Please cc the MPTCP list next time)
On 04/12/2024 09:58, MoYuanhao wrote:
> Ensure enough space before adding MPTCP options in tcp_syn_options()
> Added a check to verify sufficient remaining space
> before inserting MPTCP options in SYN packets.
> This prevents issues when space is insufficient.
Thank you for this patch. I'm surprised we all missed this check, but
yes it is missing.
As mentioned by Eric in his previous email, please add a 'Fixes' tag.
For bug-fixes, you should also Cc stable and target 'net', not 'net-next':
Fixes: cec37a6e41aa ("mptcp: Handle MP_CAPABLE options for outgoing
connections")
Cc: stable@vger.kernel.org
Regarding the code, it looks OK to me, as we did exactly that with
mptcp_synack_options(). In mptcp_established_options(), we pass
'remaining' because many MPTCP options can be set, but not here. So I
guess that's fine to keep the code like that, especially for the 'net' tree.
Also, and linked to Eric's email, did you have an issue with that, or is
it to prevent issues in the future?
One last thing, please don’t repost your patches within one 24h period, see:
https://docs.kernel.org/process/maintainer-netdev.html
Because the code is OK to me, and the same patch has already been sent
twice to the netdev ML within a few hours, I'm going to apply this patch
in our MPTCP tree with the suggested modifications. Later on, we will
send it for inclusion in the net tree.
pw-bot: awaiting-upstream
(Not sure this pw-bot instruction will work as no net/mptcp/* files have
been modified)
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2024-12-04 11:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 8:58 MoYuanhao
2024-12-04 11:01 ` Matthieu Baerts [this message]
2024-12-05 7:31 ` Mo Yuanhao
2024-12-05 7:54 ` Eric Dumazet
2024-12-05 9:24 ` Matthieu Baerts
2024-12-05 10:13 ` MoYuanhao
-- strict thread matches above, loose matches on Subject: below --
2024-12-04 3:49 MoYuanhao
2024-12-04 7:35 ` Eric Dumazet
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=80b6603d-ed52-43b7-a434-0253e5de784a@kernel.org \
--to=matttbe@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=moyuanhao3676@163.com \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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
all inboxes | Powered by JetHome®