From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: netdev@vger.kernel.org, edumazet@google.com, fan.du@windriver.com
Subject: Re: IPv6 path MTU discovery broken
Date: Mon, 7 Oct 2013 10:29:14 +0200 [thread overview]
Message-ID: <20131007082914.GA18903@sesse.net> (raw)
In-Reply-To: <20131007015252.GE9295@order.stressinduktion.org>
On Mon, Oct 07, 2013 at 03:52:52AM +0200, Hannes Frederic Sowa wrote:
>> 2001067c00a400037c4d9ae8ab73230f 80 00000000000000000000000000000000 00 fe80000000000000023048fffe555743 00000000 00000001 00000137 01000023 eth0
> Did you take the snapshot while the tcp connection was hanging? We normally
> take 2 references to the rt6_info while the tcp connection is running, this
> oddly only has one (but got used a lot). But doing a judgement on the
> reference count is imprecise.
This was while the problem was present; I had broken the TCP connection,
though.
/* Steinar */
--
Homepage: http://www.sesse.net/
next prev parent reply other threads:[~2013-10-07 8:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 20:14 IPv6 path MTU discovery broken Steinar H. Gunderson
2013-09-28 20:33 ` Hannes Frederic Sowa
2013-09-28 20:51 ` Steinar H. Gunderson
2013-09-28 21:19 ` Hannes Frederic Sowa
2013-10-06 12:06 ` Steinar H. Gunderson
2013-10-06 12:44 ` Hannes Frederic Sowa
2013-10-06 12:48 ` Steinar H. Gunderson
2013-10-07 1:52 ` Hannes Frederic Sowa
2013-10-07 3:09 ` Hannes Frederic Sowa
2013-10-07 8:32 ` Steinar H. Gunderson
2013-10-07 14:32 ` Hannes Frederic Sowa
2013-10-07 14:34 ` Steinar H. Gunderson
2013-10-07 15:49 ` Eric Dumazet
2013-10-13 10:40 ` Steinar H. Gunderson
2013-10-13 16:51 ` Eric Dumazet
2013-10-13 17:56 ` Hannes Frederic Sowa
2013-10-07 8:29 ` Steinar H. Gunderson [this message]
2013-10-07 8:37 ` Steinar H. Gunderson
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=20131007082914.GA18903@sesse.net \
--to=sgunderson@bigfoot.com \
--cc=edumazet@google.com \
--cc=fan.du@windriver.com \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.