> Note that I am not sure we correctly test that a second connect() can be > done, and I am not sure kernel would check that the remote IP and > destination port is the same.
> Ie what should happen for > setsockopt(fd, SOL_TCP, TCP_FASTOPEN_CONNECT, &on, 4) > connect(fd, "1.2.3.4:80") > connect(fd, "55.66.77.88:4000") I wrote a simple code to test this scenario and the second connect() returns EISCONN as well even though the destination IP is different. On Wed, Jan 25, 2017 at 11:03 AM, David Miller <da...@davemloft.net> wrote: > From: Wei Wang <tracyw...@gmail.com> > Date: Wed, 25 Jan 2017 10:54:50 -0800 > >>> Yes sorry David, for me it's OK. If Wei runs his whole series of tests >>> on it again, it should be perfect. >> >> I just ran all the TFO related tests with Willy's patch on top of this >> patch series. >> And everything passes. > > Great, I'll apply everything, thanks.
