From: David Miller <davem@davemloft.net>
To: christoph.paasch@uclouvain.be
Cc: David.Laight@ACULAB.COM, netdev@vger.kernel.org,
doug.leith@nuim.ie, ncardwell@google.com
Subject: Re: [PATCH net] tcp: Fix integer-overflows in TCP vegas
Date: Wed, 23 Jul 2014 14:53:00 -0700 (PDT) [thread overview]
Message-ID: <20140723.145300.680180435593895552.davem@davemloft.net> (raw)
In-Reply-To: <20140723111802.GB6387@cpaasch-mac>
From: 'Christoph Paasch' <christoph.paasch@uclouvain.be>
Date: Wed, 23 Jul 2014 13:18:02 +0200
> What do you (or others) think?
I think we should avoid the 64-bit operation altogether.
If you can't say for sure whether or not constraints guarantee
no overflows if you code this a certain way, add assertions.
prev parent reply other threads:[~2014-07-23 21:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 21:36 [PATCH net] tcp: Fix integer-overflows in TCP vegas Christoph Paasch
2014-07-22 21:58 ` Neal Cardwell
2014-07-23 8:38 ` David Laight
2014-07-23 11:18 ` 'Christoph Paasch'
2014-07-23 21:53 ` David Miller [this message]
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=20140723.145300.680180435593895552.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=David.Laight@ACULAB.COM \
--cc=christoph.paasch@uclouvain.be \
--cc=doug.leith@nuim.ie \
--cc=ncardwell@google.com \
--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).