From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: runningdoglackey@yahoo.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: Problems with /proc/net/tcp6 - possible bug - ipv6
Date: Mon, 24 Jan 2011 14:31:41 -0800 (PST) [thread overview]
Message-ID: <20110124.143141.104045281.davem@davemloft.net> (raw)
In-Reply-To: <1295732444.2651.68.camel@edumazet-laptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Sat, 22 Jan 2011 22:40:44 +0100
> Le samedi 22 janvier 2011 à 22:20 +0100, Eric Dumazet a écrit :
>> Le samedi 22 janvier 2011 à 11:42 -0800, PK a écrit :
>> > Eric Dumazet wrote:
>> > >
>> > > 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
I'm looking into this, thanks guys.
next prev parent reply other threads:[~2011-01-24 22:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <702550.61465.qm@web63902.mail.re1.yahoo.com>
2011-01-22 8:59 ` Problems with /proc/net/tcp6 - possible bug - ipv6 Eric Dumazet
2011-01-22 15:15 ` Eric Dumazet
2011-01-22 19:42 ` PK
2011-01-22 21:20 ` Eric Dumazet
2011-01-22 21:40 ` Eric Dumazet
2011-01-24 22:31 ` David Miller [this message]
2011-01-24 22:40 ` David Miller
2011-01-25 0:02 ` David Miller
2011-01-24 22:42 ` David Miller
2011-01-31 22:51 PK
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=20110124.143141.104045281.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=runningdoglackey@yahoo.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).