Le samedi 22 janvier 2011 à 22:20 +0100, Eric Dumazet a écrit :
Le samedi 22 janvier 2011 à 11:42 -0800, PK a écrit :
quoted
Eric Dumazet wrote:
quoted
I had some incidents, after hours of testing...
After following patch, I could not reproduce it.
Looks like that patch solved the /proc/net/tcp6 problem. The causal commit was
the one you identified... confirmed with bisect.
These warnings show up when I run the script (or I presume any tcp6 connection
flooder) with /proc/sys/net/tcp/ipv4/tcp_tw_recycle enabled. There's textual
corruption of the traces a lot of the time. Here's a sample trace that doesn't
appear to be corrupt. All the warnings I've seen are from route.c:209, and I
don't see how that would cause memory corruption.
Thats a different isse, already reported, under investigation.
David did some changes recently
http://comments.gmane.org/gmane.linux.network/179874
In my testings, I even have crashes in cleanup_once() if I
enable /proc/sys/net/ipv4/tcp_tw_recycle