lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8808b243f73ec97476965030c03be708@codeaurora.org>
Date:   Fri, 28 Sep 2018 10:20:54 -0600
From:   stranche@...eaurora.org
To:     Eric Dumazet <eric.dumazet@...il.com>
Cc:     Yuchung Cheng <ycheng@...gle.com>, soheil@...gle.com,
        netdev@...r.kernel.org
Subject: Re: WARN_ON in TLP causing RT throttling

On 2018-09-27 18:25, Eric Dumazet wrote:
> On 09/27/2018 05:16 PM, stranche@...eaurora.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 receive side to see if TFO would 
>> trigger this scenario, but
>> have not been able to reproduce it.
>> 
>> One other interesting thing we found is that the socket never sent or 
>> received any data. It only
>> sent/received the packets for the initial handshake and the outgoing 
>> FIN.
> 
> Just to make sure : Was this some sort of syzkaller (or other fuzzer) 
> run ?

No, this was a normal run.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ