Re: [REGRESSION] Warning in tcp_fastretrans_alert() of net/ipv4/tcp_input.c

2017-09-28 Thread Yuchung Cheng
On Thu, Sep 28, 2017 at 1:14 AM, Oleksandr Natalenko wrote: > Hi. > > Won't tell about panic in tcp_sacktag_walk() since I cannot trigger it > intentionally, but setting net.ipv4.tcp_retrans_collapse to 0 *does not* fix > warning in tcp_fastretrans_alert() for me. Hi

Re: [REGRESSION] Warning in tcp_fastretrans_alert() of net/ipv4/tcp_input.c

2017-09-28 Thread Yuchung Cheng
On Thu, Sep 28, 2017 at 1:14 AM, Oleksandr Natalenko wrote: > Hi. > > Won't tell about panic in tcp_sacktag_walk() since I cannot trigger it > intentionally, but setting net.ipv4.tcp_retrans_collapse to 0 *does not* fix > warning in tcp_fastretrans_alert() for me. Hi Oleksandr: no

Re: [REGRESSION] Warning in tcp_fastretrans_alert() of net/ipv4/tcp_input.c

2017-09-28 Thread Oleksandr Natalenko
Hi. Won't tell about panic in tcp_sacktag_walk() since I cannot trigger it intentionally, but setting net.ipv4.tcp_retrans_collapse to 0 *does not* fix warning in tcp_fastretrans_alert() for me. On středa 27. září 2017 2:18:32 CEST Yuchung Cheng wrote: > On Tue, Sep 26, 2017 at 5:12 PM,

Re: [REGRESSION] Warning in tcp_fastretrans_alert() of net/ipv4/tcp_input.c

2017-09-28 Thread Oleksandr Natalenko
Hi. Won't tell about panic in tcp_sacktag_walk() since I cannot trigger it intentionally, but setting net.ipv4.tcp_retrans_collapse to 0 *does not* fix warning in tcp_fastretrans_alert() for me. On středa 27. září 2017 2:18:32 CEST Yuchung Cheng wrote: > On Tue, Sep 26, 2017 at 5:12 PM,

Re: [REGRESSION] Warning in tcp_fastretrans_alert() of net/ipv4/tcp_input.c

2017-09-26 Thread Yuchung Cheng
On Tue, Sep 26, 2017 at 5:12 PM, Yuchung Cheng wrote: > On Tue, Sep 26, 2017 at 6:10 AM, Roman Gushchin wrote: >>> On Wed, Sep 20, 2017 at 6:46 PM, Roman Gushchin wrote: >>> > >>> > > Hello. >>> > > >>> > > Since, IIRC, v4.11, there is some

Re: [REGRESSION] Warning in tcp_fastretrans_alert() of net/ipv4/tcp_input.c

2017-09-26 Thread Yuchung Cheng
On Tue, Sep 26, 2017 at 5:12 PM, Yuchung Cheng wrote: > On Tue, Sep 26, 2017 at 6:10 AM, Roman Gushchin wrote: >>> On Wed, Sep 20, 2017 at 6:46 PM, Roman Gushchin wrote: >>> > >>> > > Hello. >>> > > >>> > > Since, IIRC, v4.11, there is some regression in TCP stack resulting in >>> > > the >>>

Re: [REGRESSION] Warning in tcp_fastretrans_alert() of net/ipv4/tcp_input.c

2017-09-26 Thread Yuchung Cheng
On Tue, Sep 26, 2017 at 6:10 AM, Roman Gushchin wrote: >> On Wed, Sep 20, 2017 at 6:46 PM, Roman Gushchin wrote: >> > >> > > Hello. >> > > >> > > Since, IIRC, v4.11, there is some regression in TCP stack resulting in >> > > the >> > > warning shown below. Most of the

Re: [REGRESSION] Warning in tcp_fastretrans_alert() of net/ipv4/tcp_input.c

2017-09-26 Thread Yuchung Cheng
On Tue, Sep 26, 2017 at 6:10 AM, Roman Gushchin wrote: >> On Wed, Sep 20, 2017 at 6:46 PM, Roman Gushchin wrote: >> > >> > > Hello. >> > > >> > > Since, IIRC, v4.11, there is some regression in TCP stack resulting in >> > > the >> > > warning shown below. Most of the time it is harmless, but

Re: [REGRESSION] Warning in tcp_fastretrans_alert() of net/ipv4/tcp_input.c

2017-09-26 Thread Roman Gushchin
> On Wed, Sep 20, 2017 at 6:46 PM, Roman Gushchin wrote: > > > > > Hello. > > > > > > Since, IIRC, v4.11, there is some regression in TCP stack resulting in the > > > warning shown below. Most of the time it is harmless, but rarely it just > > > causes either freeze or (I believe,

Re: [REGRESSION] Warning in tcp_fastretrans_alert() of net/ipv4/tcp_input.c

2017-09-26 Thread Roman Gushchin
> On Wed, Sep 20, 2017 at 6:46 PM, Roman Gushchin wrote: > > > > > Hello. > > > > > > Since, IIRC, v4.11, there is some regression in TCP stack resulting in the > > > warning shown below. Most of the time it is harmless, but rarely it just > > > causes either freeze or (I believe, this is related

Re: [REGRESSION] Warning in tcp_fastretrans_alert() of net/ipv4/tcp_input.c

2017-09-21 Thread Yuchung Cheng
On Wed, Sep 20, 2017 at 6:46 PM, Roman Gushchin wrote: > > > Hello. > > > > Since, IIRC, v4.11, there is some regression in TCP stack resulting in the > > warning shown below. Most of the time it is harmless, but rarely it just > > causes either freeze or (I believe, this is related

Re: [REGRESSION] Warning in tcp_fastretrans_alert() of net/ipv4/tcp_input.c

2017-09-21 Thread Yuchung Cheng
On Wed, Sep 20, 2017 at 6:46 PM, Roman Gushchin wrote: > > > Hello. > > > > Since, IIRC, v4.11, there is some regression in TCP stack resulting in the > > warning shown below. Most of the time it is harmless, but rarely it just > > causes either freeze or (I believe, this is related too) panic in

Re: [REGRESSION] Warning in tcp_fastretrans_alert() of net/ipv4/tcp_input.c

2017-09-20 Thread Roman Gushchin
> Hello. > > Since, IIRC, v4.11, there is some regression in TCP stack resulting in the > warning shown below. Most of the time it is harmless, but rarely it just > causes either freeze or (I believe, this is related too) panic in > tcp_sacktag_walk() (because sk_buff passed to this function is

Re: [REGRESSION] Warning in tcp_fastretrans_alert() of net/ipv4/tcp_input.c

2017-09-20 Thread Roman Gushchin
> Hello. > > Since, IIRC, v4.11, there is some regression in TCP stack resulting in the > warning shown below. Most of the time it is harmless, but rarely it just > causes either freeze or (I believe, this is related too) panic in > tcp_sacktag_walk() (because sk_buff passed to this function is

[REGRESSION] Warning in tcp_fastretrans_alert() of net/ipv4/tcp_input.c

2017-09-10 Thread Oleksandr Natalenko
Hello. Since, IIRC, v4.11, there is some regression in TCP stack resulting in the warning shown below. Most of the time it is harmless, but rarely it just causes either freeze or (I believe, this is related too) panic in tcp_sacktag_walk() (because sk_buff passed to this function is NULL).

[REGRESSION] Warning in tcp_fastretrans_alert() of net/ipv4/tcp_input.c

2017-09-10 Thread Oleksandr Natalenko
Hello. Since, IIRC, v4.11, there is some regression in TCP stack resulting in the warning shown below. Most of the time it is harmless, but rarely it just causes either freeze or (I believe, this is related too) panic in tcp_sacktag_walk() (because sk_buff passed to this function is NULL).