On Thu, Sep 27, 2018 at 5:16 PM, wrote:
>
> On 2018-09-27 13:14, Yuchung Cheng wrote:
>>
>> On Wed, Sep 26, 2018 at 5:09 PM, Eric Dumazet wrote:
>>>
>>>
>>>
>>>
>>> On 09/26/2018 04:46 PM, stran...@codeaurora.org wrote:
>>> > Hi Eric,
>>> >
>>> > Someone recently reported a crash to us on the
On 2018-09-27 18:25, Eric Dumazet wrote:
On 09/27/2018 05:16 PM, stran...@codeaurora.org wrote:
Hi Yuchung,
Based on the dumps we were able to get, it appears that TFO was not
used in this case.
We also tried some local experiments where we dropped incoming SYN
packets after already
On 09/27/2018 05:16 PM, stran...@codeaurora.org wrote:
> Hi Yuchung,
>
> Based on the dumps we were able to get, it appears that TFO was not used in
> this case.
> We also tried some local experiments where we dropped incoming SYN packets
> after already
> successful TFO connections on the
On 2018-09-27 13:14, Yuchung Cheng wrote:
On Wed, Sep 26, 2018 at 5:09 PM, Eric Dumazet
wrote:
On 09/26/2018 04:46 PM, stran...@codeaurora.org wrote:
> Hi Eric,
>
> Someone recently reported a crash to us on the 4.14.62 kernel where excessive
> WARNING prints were spamming the logs and
On Wed, Sep 26, 2018 at 5:09 PM, Eric Dumazet wrote:
>
>
>
> On 09/26/2018 04:46 PM, stran...@codeaurora.org wrote:
> > Hi Eric,
> >
> > Someone recently reported a crash to us on the 4.14.62 kernel where
> > excessive
> > WARNING prints were spamming the logs and causing watchdog bites. The
On 09/26/2018 04:46 PM, stran...@codeaurora.org wrote:
> Hi Eric,
>
> Someone recently reported a crash to us on the 4.14.62 kernel where excessive
> WARNING prints were spamming the logs and causing watchdog bites. The kernel
> does have the following commit by Soheil:
> bffd168c3fc5 "tcp:
