From: Eric Dumazet <eric.dumazet@gmail.com>
To: stranche@codeaurora.org, Yuchung Cheng <ycheng@google.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
soheil@google.com, netdev@vger.kernel.org
Subject: Re: WARN_ON in TLP causing RT throttling
Date: Thu, 27 Sep 2018 17:25:53 -0700 [thread overview]
Message-ID: <7e05c738-8188-8cae-a726-33f780f6b05f@gmail.com> (raw)
In-Reply-To: <f4103fc7d67dff06718bbc5a992170cb@codeaurora.org>
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 ?
next prev parent reply other threads:[~2018-09-28 6:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 23:46 WARN_ON in TLP causing RT throttling stranche
2018-09-27 0:09 ` Eric Dumazet
2018-09-27 19:14 ` Yuchung Cheng
2018-09-28 0:16 ` stranche
2018-09-28 0:25 ` Eric Dumazet [this message]
2018-09-28 16:20 ` stranche
2018-10-02 21:19 ` Yuchung Cheng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7e05c738-8188-8cae-a726-33f780f6b05f@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=soheil@google.com \
--cc=stranche@codeaurora.org \
--cc=ycheng@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).