Re: Badness at net/ipv4/inet_connection_sock.c:293

[lists]

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)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/