From: Matthieu Baerts <matttbe@kernel.org>
To: Dmitry Kandybka <d.kandybka@gmail.com>
Cc: mptcp@lists.linux.dev, netdev@vger.kernel.org,
lvc-project@linuxtesting.org,
Dmitry Antipov <dmantipov@yandex.ru>
Subject: Re: [PATCH] mptcp: fix possible integer overflow in mptcp_reset_tout_timer
Date: Fri, 8 Nov 2024 12:43:48 +0100 [thread overview]
Message-ID: <5f51673a-e19b-45e8-bb1c-a6d3427213c1@kernel.org> (raw)
In-Reply-To: <20241107103657.1560536-1-d.kandybka@gmail.com>
Hi Dmitry,
On 07/11/2024 11:36, Dmitry Kandybka wrote:
> In 'mptcp_reset_tout_timer', promote 'probe_timestamp' to unsigned long
> to avoid possible integer overflow. Compile tested only.
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
> Signed-off-by: Dmitry Kandybka <d.kandybka@gmail.com>
> ---
> net/mptcp/protocol.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/net/mptcp/protocol.c b/net/mptcp/protocol.c
> index e978e05ec8d1..ff2b8a2bfe18 100644
> --- a/net/mptcp/protocol.c
> +++ b/net/mptcp/protocol.c
> @@ -2722,8 +2722,8 @@ void mptcp_reset_tout_timer(struct mptcp_sock *msk, unsigned long fail_tout)
> if (!fail_tout && !inet_csk(sk)->icsk_mtup.probe_timestamp)
> return;
>
> - close_timeout = inet_csk(sk)->icsk_mtup.probe_timestamp - tcp_jiffies32 + jiffies +
> - mptcp_close_timeout(sk);
> + close_timeout = (unsigned long)inet_csk(sk)->icsk_mtup.probe_timestamp -
> + tcp_jiffies32 + jiffies + mptcp_close_timeout(sk);
If I'm not mistaken, "jiffies" is an "unsigned long", which makes this
modification not necessary, no?
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2024-11-08 11:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 10:36 [PATCH] mptcp: fix possible integer overflow in mptcp_reset_tout_timer Dmitry Kandybka
2024-11-08 11:43 ` Matthieu Baerts [this message]
2024-11-08 21:42 ` Fedor Pchelkin
2024-11-12 11:55 ` Paolo Abeni
2024-11-13 5:00 ` patchwork-bot+netdevbpf
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=5f51673a-e19b-45e8-bb1c-a6d3427213c1@kernel.org \
--to=matttbe@kernel.org \
--cc=d.kandybka@gmail.com \
--cc=dmantipov@yandex.ru \
--cc=lvc-project@linuxtesting.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).