From mboxrd@z Thu Jan 1 00:00:00 1970 From: stranche@codeaurora.org Subject: Re: WARN_ON in TLP causing RT throttling Date: Fri, 28 Sep 2018 10:20:54 -0600 Message-ID: <8808b243f73ec97476965030c03be708@codeaurora.org> References: <7aa9932a59aad7a21c7f8a8146dd0542@codeaurora.org> <3c112d25-1105-524f-e210-8a7cb63df1c7@gmail.com> <7e05c738-8188-8cae-a726-33f780f6b05f@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Cc: Yuchung Cheng , soheil@google.com, netdev@vger.kernel.org To: Eric Dumazet Return-path: Received: from smtp.codeaurora.org ([198.145.29.96]:58396 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728972AbeI1WpZ (ORCPT ); Fri, 28 Sep 2018 18:45:25 -0400 In-Reply-To: <7e05c738-8188-8cae-a726-33f780f6b05f@gmail.com> Sender: netdev-owner@vger.kernel.org List-ID: On 2018-09-27 18:25, Eric Dumazet wrote: > On 09/27/2018 05:16 PM, stranche@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 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.