From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: linux-sctp@vger.kernel.org
Subject: Re: [Lksctp-developers] [PATCH 2/3] sctp: fix integer overflow when
Date: Thu, 12 Nov 2009 16:29:17 +0000 [thread overview]
Message-ID: <4AFC37DD.8090605@hp.com> (raw)
Andrei Pelinescu-Onciul wrote:
> When setting the autoclose timeout in jiffies there is a possible
> integer overflow if the value in seconds is very large
> (e.g. for 2^22 s with HZ\x1024). The problem appears even on
> 64-bit due to the integer promotion rules. The fix is just a cast
> to unsigned long.
>
> Signed-off-by: Andrei Pelinescu-Onciul <andrei@iptel.org>
> ---
> net/sctp/associola.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/net/sctp/associola.c b/net/sctp/associola.c
> index 525864b..7f69f4d 100644
> --- a/net/sctp/associola.c
> +++ b/net/sctp/associola.c
> @@ -166,7 +166,7 @@ static struct sctp_association *sctp_association_init(struct sctp_association *a
> asoc->timeouts[SCTP_EVENT_TIMEOUT_HEARTBEAT] = 0;
> asoc->timeouts[SCTP_EVENT_TIMEOUT_SACK] = asoc->sackdelay;
> asoc->timeouts[SCTP_EVENT_TIMEOUT_AUTOCLOSE] > - sp->autoclose * HZ;
> + (unsigned long)sp->autoclose * HZ;
>
> /* Initilizes the timers */
> for (i = SCTP_EVENT_TIMEOUT_NONE; i < SCTP_NUM_TIMEOUT_TYPES; ++i)
This becomes unnecessary with Patch 3.
-vlad
next reply other threads:[~2009-11-12 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 16:29 Vlad Yasevich [this message]
2009-11-12 16:49 ` [Lksctp-developers] [PATCH 2/3] sctp: fix integer overflow when setting the autoclose timer Andrei Pelinescu-Onciul
2009-11-12 17:05 ` [Lksctp-developers] [PATCH 2/3] sctp: fix integer overflow when Vlad Yasevich
2009-11-12 17:16 ` [Lksctp-developers] [PATCH 2/3] sctp: fix integer overflow when setting the autoclose timer Andrei Pelinescu-Onciul
2009-11-12 17:34 ` [Lksctp-developers] [PATCH 2/3] sctp: fix integer overflow when Vlad Yasevich
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=4AFC37DD.8090605@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=linux-sctp@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 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.