From: Eric Dumazet <hidden> Date: 2017-05-01 22:29:51
From: Eric Dumazet <edumazet@google.com>
Be careful when comparing tcp_time_stamp to some u32 quantity,
otherwise result can be surprising.
Fixes: 7c106d7e782b ("[TCP]: TCP Low Priority congestion control")
Signed-off-by: Eric Dumazet <edumazet@google.com>
---
net/ipv4/tcp_lp.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
From: Stephen Hemminger <stephen@networkplumber.org> Date: 2017-05-01 23:56:46
On Mon, 01 May 2017 15:29:48 -0700
Eric Dumazet [off-list ref] wrote:
quoted hunk
From: Eric Dumazet <edumazet@google.com>
Be careful when comparing tcp_time_stamp to some u32 quantity,
otherwise result can be surprising.
Fixes: 7c106d7e782b ("[TCP]: TCP Low Priority congestion control")
Signed-off-by: Eric Dumazet <edumazet@google.com>
---
net/ipv4/tcp_lp.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
On Mon, May 1, 2017 at 7:56 PM, Stephen Hemminger
[off-list ref] wrote:
On Mon, 01 May 2017 15:29:48 -0700
Agreed time wraparound would cause problems.
But why not use existing time_after() macro here?
I suspect this is because time_after() asserts that it is being used
on unsigned long (64 bits), and tcp_time_stamp is 32 bits.
I suppose for tcp_time_stamp comparisons we could re-use the u32 TCP
sequence macros for before() and after()? Even the comment for
before()/after() is already generic enough to apply to tcp_time_stamp:
"The next routines deal with comparing 32 bit unsigned ints and worry
about wraparound (automatic with unsigned arithmetic)." That might be
nice.
neal
From: Eric Dumazet <hidden> Date: 2017-05-02 01:04:51
On Mon, 2017-05-01 at 16:56 -0700, Stephen Hemminger wrote:
On Mon, 01 May 2017 15:29:48 -0700
Eric Dumazet [off-list ref] wrote:
quoted
From: Eric Dumazet <edumazet@google.com>
Be careful when comparing tcp_time_stamp to some u32 quantity,
otherwise result can be surprising.
Fixes: 7c106d7e782b ("[TCP]: TCP Low Priority congestion control")
Signed-off-by: Eric Dumazet <edumazet@google.com>
---
net/ipv4/tcp_lp.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
Agreed time wraparound would cause problems.
But why not use existing time_after() macro here?
Simply to not perform (tcp_time_stamp - tp->rx_opt.rcv_tsecr) twice.
jiffies being volatile, this can not be optimized by the compiler.
I have a patch series (for linux-4.13) that will switch TCP stack to 1ms
TS options, regardless of CONFIG_HZ value, and when cooking it I found
this bug.
From: Eric Dumazet <hidden> Date: 2017-05-02 01:58:37
On Mon, 2017-05-01 at 18:04 -0700, Eric Dumazet wrote:
Simply to not perform (tcp_time_stamp - tp->rx_opt.rcv_tsecr) twice.
jiffies being volatile, this can not be optimized by the compiler.
I have a patch series (for linux-4.13) that will switch TCP stack to 1ms
TS options, regardless of CONFIG_HZ value, and when cooking it I found
this bug.
I forgot to say that after this upcoming patch series, tcp_time_stamp
will become a more expensive function, no longer a plain (u32)jiffies.
From: David Miller <davem@davemloft.net> Date: 2017-05-02 19:07:31
From: Eric Dumazet <redacted>
Date: Mon, 01 May 2017 15:29:48 -0700
From: Eric Dumazet <edumazet@google.com>
Be careful when comparing tcp_time_stamp to some u32 quantity,
otherwise result can be surprising.
Fixes: 7c106d7e782b ("[TCP]: TCP Low Priority congestion control")
Signed-off-by: Eric Dumazet <edumazet@google.com>