lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <80b6603d-ed52-43b7-a434-0253e5de784a@kernel.org>
Date: Wed, 4 Dec 2024 12:01:32 +0100
From: Matthieu Baerts <matttbe@...nel.org>
To: MoYuanhao <moyuanhao3676@....com>, edumazet@...gle.com,
 davem@...emloft.net, dsahern@...nel.org, kuba@...nel.org, pabeni@...hat.com,
 horms@...nel.org
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
 martineau@...nel.org, geliang@...nel.org, MPTCP Linux <mptcp@...ts.linux.dev>
Subject: Re: [PATCH net-next] tcp: Check space before adding MPTCP options

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@...r.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.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ