From: Joe Perches <joe@perches.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Yuchung Cheng <ycheng@google.com>,
David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Neal Cardwell <ncardwell@google.com>
Subject: Re: [PATCH net-next] tcp: avoid possible arithmetic overflows
Date: Sat, 20 Sep 2014 13:19:52 -0700 [thread overview]
Message-ID: <1411244392.10610.4.camel@joe-AO725> (raw)
In-Reply-To: <1411242956.26859.81.camel@edumazet-glaptop2.roam.corp.google.com>
On Sat, 2014-09-20 at 12:55 -0700, Eric Dumazet wrote:
> On Sat, 2014-09-20 at 12:46 -0700, Yuchung Cheng wrote:
> > On Sat, Sep 20, 2014 at 11:01 AM, Joe Perches <joe@perches.com> wrote:
> > > On Sat, 2014-09-20 at 10:19 -0700, Eric Dumazet wrote:
> > >> From: Eric Dumazet <edumazet@google.com>
> > >>
> > >> icsk_rto is an 32bit field, and icsk_backoff can reach 15 by default,
> > >> or more if some sysctl (eg tcp_retries2) are changed.
> > >>
> > >> Better use 64bit to perform icsk_rto << icsk_backoff operations
> > >
> > > Maybe better to use a helper function for this?
> > >
> > > something like:
> > >
> > > static inline u64 icsk_rto_backoff(const struct inet_connection_sock *icsk)
> > > {
> > > u64 when = (u64)icsk->icsk_rto;
> > >
> > > return when << icsk->icsk_backoff;
> > > }
> > Thanks for the fix Eric. I second Joe's idea to use a helper function.
> >
>
> Yep.
>
> Given the timeout functions in the kernel use 'unsigned long', I prefer
> to keep the u64 magic private to this helper.
>
> I will probably use
>
> static inline unsigned long icsk_rto_backoff(const struct inet_connection_sock *icsk)
> {
> u64 when = (u64)icsk->icsk_rto << icsk->icsk_backoff;
>
> return min_t(u64, when, ~0UL);
OK.
I think an explicit cast to unsigned long after the min_t
to avoid the implicit downcast would be better
return (unsigned long)min_t(etc...)
so that no warning is produced if someone does make W=3
next prev parent reply other threads:[~2014-09-20 20:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-20 17:19 [PATCH net-next] tcp: avoid possible arithmetic overflows Eric Dumazet
2014-09-20 18:01 ` Joe Perches
2014-09-20 19:46 ` Yuchung Cheng
2014-09-20 19:55 ` Eric Dumazet
2014-09-20 20:19 ` Joe Perches [this message]
2014-09-21 0:29 ` [PATCH v2 " Eric Dumazet
2014-09-21 17:46 ` Yuchung Cheng
2014-09-22 12:42 ` Eric Dumazet
2014-09-22 20:19 ` [PATCH v3 " Eric Dumazet
2014-09-22 20:27 ` David Miller
2014-09-22 20:28 ` Eric Dumazet
2014-09-22 3:56 ` [PATCH v2 " Joe Perches
2014-09-22 11:13 ` [PATCH " David Laight
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=1411244392.10610.4.camel@joe-AO725 \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=ycheng@google.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;
as well as URLs for NNTP newsgroup(s).