Re: net-next: WARNING: CPU: 0 PID: 1544 at net/ipv4/tcp_input.c:889

2017-10-16 Thread Eric Dumazet
On Mon, Oct 16, 2017 at 4:11 PM, Andrei Vagin wrote: > Hi Eric, > > Could you take a look at this warning? It may be related with your > recent patches. First time we saw this warning 7 days ago > (net-next/master) and now we see it regularly. > > I printed tp->fackets_out and state->reord before

Re: net-next: WARNING: CPU: 0 PID: 1544 at net/ipv4/tcp_input.c:889

2017-10-16 Thread Andrei Vagin
Hi Eric, Could you take a look at this warning? It may be related with your recent patches. First time we saw this warning 7 days ago (net-next/master) and now we see it regularly. I printed tp->fackets_out and state->reord before the warnings and here are values for them: tp->fackets_out = -1 s

net-next: WARNING: CPU: 0 PID: 1544 at net/ipv4/tcp_input.c:889

2017-10-09 Thread Andrei Vagin
Hello, We run CRIU tests on a daily basis for net-next and today they triggered a following warning: [ 58.827039] [ cut here ] [ 58.827078] WARNING: CPU: 0 PID: 1544 at net/ipv4/tcp_input.c:889 tcp_update_reordering+0x9f/0xb0 [ 58.827083] Modules linked in: [ 58.8