lkml.org 
[lkml]   [2009]   [Dec]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Badness at net/ipv4/inet_connection_sock.c:293
On Sat, 12 Dec 2009 at 10:22, Eric Dumazet wrote:
> > Yeah I started seeing this on one of my machines too, the
> > assertion is:
> >
> > WARN_ON(newsk->sk_state == TCP_SYN_RECV);
> >
> > I wonder if some of the refactorings we did to allow per-route
> > SACK/DSACK/etc. controls messed some sequence of state changes
> > on TCP sockets. But I can't find anything obvious in those
> > commits.
>
> Could it be about syncookies patches ?
> tcp_create_openreq_child() changes ?

Hm, I'd like to reproduce this thing and just ran "siege" against the
proxy, spawning > 10k connections (simliar to when the warnings appeared)
but I can't trigger the message any more. I'm tempted to bisect, but this
is no fun when I cannot reproduce the messages :-\

Christian.
--
BOFH excuse #140:

LBNC (luser brain not connected)


\
 
 \ /
  Last update: 2009-12-12 11:09    [W:0.062 / U:0.524 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site